Skip to content

docs: v3-first documentation, v2 archived under a legacy section - #233

Open
afonsojramos wants to merge 11 commits into
mainfrom
v3
Open

docs: v3-first documentation, v2 archived under a legacy section#233
afonsojramos wants to merge 11 commits into
mainfrom
v3

Conversation

@afonsojramos

Copy link
Copy Markdown
Member

Rewrites the site around Spicetify v3, keeping every v2 page under /docs/legacy so nothing that is indexed 404s. Open as a preview: the install pages assume a published v3 release, so this should land close to the first v3* tag rather than before it.

What changes

  • New v3 tree: install and first module, what changes from v2, modules and the store, config.toml reference, a CLI reference written from the binary's own --help, and building + publishing a module.
  • v2 archived under /docs/legacy, each page carrying a banner that links to its v3 equivalent, with a redirect for every URL that moved.
  • API reference verified against a live v3 client (Spotify 1.2.94): the Panel surface and GraphQL.Definitions are gone, PlatformData lost three documented fields and gained three undocumented ones, and isPlaylistV2URI is now isPlaylistV2. Those pages say so.
  • Removes the duplicate root docs/ tree. Only src/content/docs builds; the two were kept in sync by hand, and PR Fix broken Themes → Marketplace relative link #222 had to patch both.

Verification

  • bun run build — 101 pages
  • oxlint and oxfmt --check clean
  • Every internal /docs link and sidebar entry resolves against a page that exists or a redirect (95 pages, 23 redirects)

Note before merging

install.sh --v3 and the Windows $v3 one-liner only become true statements once a v3* release exists. Merge alongside the first beta tag.

oxfmt ignores md, mdx, yaml, html and css, but lint-staged handed it
exactly those types, so any commit whose staged set was entirely markdown
(most commits in a docs repo) died on "Expected at least one target
file". The glob now matches what oxfmt actually formats.
The site described v2 exclusively. The main tree is now v3 (install and
first module, what changes from v2, modules and the store, config.toml,
the CLI reference written from the binary's own help, building and
publishing a module), and every v2 page keeps its content under
/docs/legacy behind a banner pointing at its v3 equivalent, with a
redirect for each URL that moved.

The API reference is shared by both and was checked against a running v3
client: the Panel surface and GraphQL.Definitions are gone, PlatformData
lost three documented fields and gained three undocumented ones, and
isPlaylistV2URI is isPlaylistV2. Those pages now say so.

Also removes the duplicate root docs/ tree. Only src/content/docs builds,
the two were kept in sync by hand, and PR #222 had to patch both.
…ction rules

Getting started and the CLI reference now say a fresh apply seeds stdlib and
the store, which is what makes the store present without a manual install.
The trashbin enable examples used a real version that would age, so they
point at the version pkg install prints. Also removes the horizontal rules
between sections and one 'should'.
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Aug 10, 2026

Copy link
Copy Markdown

Deploying spicetify-docs with  Cloudflare Pages  Cloudflare Pages

Latest commit: a992031
Status: ✅  Deploy successful!
Preview URL: https://1ae67f62.spicetify-docs.pages.dev
Branch Preview URL: https://v3.spicetify-docs.pages.dev

View logs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant