Documentation versions
Understand current documentation, immutable snapshots, and support policy.
The documentation follows the API. /docs always describes the current development line deployed from main. Starting with the first public release, immutable snapshots use /docs/v/<version>/… and keep their generated API, examples, package versions, and AI artifacts together.
Current status
The packages currently report version 0.0.0. This is an experimental development line, not a stable documentation release. There are no immutable public snapshots yet.
When the first version is released, the snapshot process will:
- build and validate the current docs and generated catalog;
- store processed MDX, generated API JSON, and example sources under that version;
- pin the exact package versions in the snapshot manifest;
- add the snapshot to the version selector;
- stop normal development from modifying it.
Link policy
- Use
/docs/...for the latest guidance. - Use
/docs/v/<version>/...in long-lived articles, training material, and support answers tied to a package release. - Do not mix a current component API route with an older installation page.
Pre-release snapshots may be retained when they are useful for migration. A snapshot's presence records documentation history; it does not imply ongoing maintenance for that package version.