Built to be read twice.
For the part of the site that is all detail. A persistent contents column, anchored headings and a search that only looks inside the docs.
Documentation is read twice: once end to end while learning, and a hundred times afterwards in fragments. The layout serves the second case, because that is the one that generates support tickets.
Every heading is an anchor, every code block knows its language, and search is scoped to the documentation rather than dragging in blog posts from four years ago.
Support tickets went down. I am counting that as a win.
— A product lead
Documentation, second reading.
Anchored everything
Every heading down to the fourth level has a stable, copyable anchor that survives page reordering.
Versioned pages
Documentation for older releases stays online at its own address instead of being overwritten.
Tabbed code samples
Language tabs that remember the reader choice across every page of the documentation.
Scoped search
Search that looks only inside the docs, ranking headings above body text and exact matches above both.
Page feedback
A one-click was-this-useful control whose answers land in an admin report rather than a third-party service.
Reference features, not tutorial ones.
Built for the hundredth visit rather than the first, because that is the visit that generates support tickets.
- Stable anchors to heading level four
- Version-scoped documentation trees
- Language tabs with a remembered choice
- Documentation-only search index
- Was-this-useful feedback log
- Copy button on every code block
- Callout blocks for warnings and notes
- Keyboard shortcut overlay
- Deprecation banners with dates
The details
- Version
- 2.1.4
- Released
- Feb 28, 2026
- Anchor depth
- Four levels
- Versioning
- Per release tree
- Search scope
- Docs only
- Feedback
- Stored locally
Recent releases
- 2.1.4Feb 2026 — Anchors now survive a page being renamed
- 2.1.3Jan 2026 — Language tab choice shared across the whole tree
- 2.1.2Nov 2025 — Deprecation banners take an end date