Website and Docs Architecture Overview

What Lives In `website/`

The public site lives under website/. The important areas are:

website/
  content/
    docs/
  data/
    docs-nav/
    docs-versions.toml
  scripts/
  themes/sambee/
  assets/
  static/

In practice:

content/ holds the authored website pages and docs pages.
content/docs/ holds the published versioned docs books.
data/docs-versions.toml declares the canonical docs version order and the current version.
data/docs-nav/<version>.toml declares book, section, and page ordering for one version.
scripts/ holds build helpers, docs validation, docs materialization, and docs editor automation.
themes/sambee/ holds the Hugo layouts, partials, CSS, and JS for the public site.
assets/ and static/ hold source media, generated media, and static files.

Docs content is versioned in the content tree:

website/content/docs/<version>/<book>/<section>/<page>/index.md

The current docs version also publishes stable unversioned routes:

Archived or explicit versioned routes remain available at:

The routing rules, inheritance markers, and stable-current behavior are covered in more detail in Docs Content Model, Navigation, and Inheritance .

The website build is more than a plain Hugo render.

The normal production-style build is:

cd website
npm run build

That command runs:

For local development, use:

./scripts/start-website

Or run the website dev workflow directly:

cd website
npm run dev

That dev workflow also keeps search indexing and WebP generation in sync while you iterate.