Conventions

Every documentation file should be useful as a static markdown document before any React components or interactivity are added.

All useful content should be represented in the HTML without JavaScript. This ensures crawlers, screen readers, and users on slow connections can access documentation content immediately.

A consistent file structure makes it easy to find what you need. The patterns below apply across the repository.

We use `:` to express hierarchy inside URL fragments. Example: `https://example.com/page#section:subsection` uses `:` to separate a primary section (`section`) from a nested part (`subsection`). The full value appears in an element’s `id`, e.g. `section:subsection`.