Route frame
Getting started
Fast orientation for someone who needs the shortest route into templates, apps or a studio handoff.
- Route selection
- First deployment steps
- Where the studio takes over
Docs and guides
Route notes
for a system
that keeps growing.
Docs should help someone move through the world without overpromising what is not product-ready yet. This lane is for clarity, sequencing and cleaner expectations.
01
Three layers of clarity.
Fast orientation, deeper guides and sharper reference notes. That split helps the world stay readable as routes multiply.
Route frame
Guides
Longer explanations for why routes exist, how they differ and when to move from one layer to another.
- Sequencing
- Hosting logic
- Template-to-builder path
Route frame
Reference
Sharper lists, notes and operating assumptions that keep the world readable as it grows.
- Capabilities
- Maturity notes
- System boundaries
02
How someone should move through the docs.
The route starts from the problem, not from a giant wall of information. That keeps the docs useful instead of turning them into decorative clutter.
Choose
Choose the route that matches the problem instead of reading the whole world like one giant brochure.
Read
Use the guide layer to understand what is active now and what is intentionally staged for later.
Launch
Move into templates, live apps or studio work with a cleaner expectation of what happens next.
Maintain
Keep the docs honest as routes gain product depth, client logic or stronger operator layers.
Next move
If the route is clear, the world can expand without becoming vague.
Docs are not there to look official. They are there to reduce friction between public proof, live routes and the heavier flagship work.