Reference
Reference pages collect durable facts that readers need to find quickly: data contracts, policies, workflow inventories, path maps, compatibility notes, and dated QA evidence.
Reference sections
Section titled “Reference sections”| Section | Contents |
|---|---|
| Mobile contracts | Mobile FlatBuffers contract notes and generated-code boundaries. |
| QA and evidence | Android/TV QA packets, playback/auth regression evidence, visual accessibility runbooks, and stale/manual-hardware status. |
| Project policies | Links to canonical GitHub policy files with the drift-prevention decision for each. |
| Crate README inventory | Package-facing README files that remain canonical outside the docs site. |
| Rust API and crate map | Workspace crate responsibilities, key public surfaces, and rustdoc/docs.rs entry points. |
| Legacy Markdown pointers | Old markdown paths and their new Starlight locations. |
Use a reference page when the reader needs a stable answer more than a tutorial. If the page mainly tells a reader how to complete a task, it belongs in an operator, developer, or release section and can link back here for definitions.