The documentation site, and the diagram the root README uses.

.github/workflows/pages.yml uploads this directory unchanged. Nothing is built, so what is committed is exactly what is served — open any page with file:// and it works.

Pages has to be switched on once by hand, under Settings → Pages → Source: GitHub Actions. Until then the deploy step fails, which is the right state for a repository that has not decided to publish.

Two rules, both of which the workflow enforces or the pages depend on.

Nothing may be loaded from the network. No CDN scripts, no remote fonts, no external stylesheets. Outbound <a href> links are fine; a remote asset is not, because it makes the page depend on someone else's uptime and fails quietly for anyone who has it cached. The deploy workflow greps for this and fails the build.

Every page carries the same <style> block. It is duplicated on purpose — that is what keeps the site buildless — so a style change means replacing that block in all eight files, not editing one. The block runs from the :root palette to the reduced-motion query and is byte-identical everywhere, so a mechanical replace is safe.

Themes are three-state: the bare :root palette is light, a prefers-color-scheme: dark block guarded with :not([data-theme="light"]) handles the System setting, and an explicit [data-theme="dark"] block lets the toggle win in both directions. Do not give a colour its only definition inside one of those blocks.