Inside of your Astro + Starlight project, you'll see the following folders and files:

.
├── public/
├── src/
│   ├── assets/
│   ├── content/
│   │   ├── docs/
│   │   └── config.ts
│   └── env.d.ts
├── astro.config.mjs
├── package.json
└── tsconfig.json

Starlight looks for .md or .mdx files in the src/content/docs/ directory. Each file is exposed as a route based on its file name.

Images can be added to src/assets/ and embedded in Markdown with a relative link.

Static assets, like favicons, can be placed in the public/ directory.

All commands are run from the root of the project, from a terminal:

npm run build:versions produces a single site where the current checkout is Latest at the root and each versioned release lives under a /<slug>/ subpath (e.g. /v0-76/).

For each release tag, hack/build-versions.mjs checks out a throwaway git worktree and stages that tag's docs content into src/content/docs/<slug>/, regenerating its examples and schema under src/assets/versioned-assets/<slug>/ from the tag's examples/ and zarf.schema.json. Archived content therefore renders with the current toolchain and components, never its own.

Versions are discovered from git tags and reduced to the newest patch per minor. Only the current major and the one before it are kept — the current major shows its last 10 minors and the previous major its latest 3 minors. The set is written to versions.json, which the version switcher reads.

Check out Starlight's docs, read the Astro documentation, or jump into the Astro Discord server.