This starter is intentionally small, so the quickest way to get oriented is to understand which files define structure and which files hold content.

What to look at first

The starter is split into a few clear layers:

  • pages/[locale]/index.tsx holds the landing page implementation, while pages/index.tsx keeps the default-locale alias.
  • pages/[locale]/docs.tsx and pages/[locale]/reference.tsx hold the collection overview implementations.
  • pages/[locale]/docs/[...slug].tsx and pages/[locale]/reference/[...slug].tsx are the shared React routes for individual content pages.
  • each [...slug].server.ts file handles prerender paths and per-page head metadata.
  • src/content/docs/**/*.md contains guide content, including nested folders.
  • src/content/reference/**/*.md contains API-oriented content.
  • src/components/docs-page.tsx bridges the current route to the right markdown page.
  • src/components/docs-shell.tsx controls the shared docs layout.
  • src/collections/collection.ts builds the metadata, sidebar groups, headings, and prev/next links for each collection.
  • void.config.ts controls static output and default metadata.

Run it locally

Use the standard Vite+ flow:

vp install
vp dev

Then open:

  • http://localhost:5173/
  • http://localhost:5173/docs

Make your first edit

A good first pass is to edit one markdown file and one layout file:

  1. Update a page in src/content/docs/ to change the actual documentation copy.
  2. Add a page in src/content/docs/guides/ if you want to test nested sidebar groups.
  3. Add a page in src/content/reference/ if you want to expand the reference section.
  4. Tweak src/components/docs-shell.tsx if you want the sidebar, heading area, or table of contents to feel different.

This separation keeps content edits lightweight while leaving the visual system centralized.

What to avoid early

It is tempting to add search, auth, API routes, or dynamic examples immediately. Resist that for the first pass. A docs site gets easier to maintain when the information architecture becomes stable before the feature list expands.

When you are ready to change how docs are written, continue with Content Authoring.