How these docs work
Three layers, one sidebar. You do not need every layer on day one.
Guide (Welcome through Ship)
Short pages in story order: write → set up → direct → stage → look → polish → ship. Read top to bottom the first time. Later, jump in from search or the sidebar.
Reference
When you already know what you want:
| Layer | Job |
|---|---|
| File maps | Whole file at a glance; every key clickable |
| Detail pages | Full tables (commands, story, screens, theme, …) |
| Shared shapes | Transitions, textures, binds, hooks — once, linked everywhere |
| Everything A–Z | Flat name list — browser search (Ctrl+F) |
Guide pages teach when; maps and detail teach every key.
Examples vs docs
examples/ | Playable, incomplete on purpose — teach a slice |
| Docs | Complete — teach the surface |
If an example does not use a key, the key still exists. Check the map or detail page for that surface.
Author tools
Overlay, jumps, flags, Validation, Build: Author tools · Build and hand off.
Checking a project
The author kit can validate your folder (broken jumps, missing assets, schema). Prefer that over guessing from memory — Reference.