Docs

The Docs App is for reference material — knowledge bases, runbooks, onboarding guides, anything you'll come back to weeks or months from now. Docs are built to last, organized into hierarchies, and explicitly meant for navigation rather than authoring sessions.

Docs vs. Pages#

A simple way to think about it: a Page is a thing you wrote; a Doc is a thing you maintain. The Pages app is the writing tool; the Docs app is the wiki.

What Docs gives you#

• Hierarchical structure — Docs nest into pages and sub-pages within a Doc tree
• Sidebar navigation — like reading any well-organized handbook
• Section permalinks — share /docs/.../page#section
• Version history — every Doc tracks edits forever; rollback is one click
• Multiplayer — like Pages, fully real-time
• Snapshots — promote a Doc state to a named version (e.g., "v1.2 onboarding")

What teams use Docs for#

• Engineering wikis — service runbooks, on-call playbooks, architecture
• Onboarding — the things new hires need
• Brand guidelines — voice, visual system, do's/don'ts
• Customer playbooks — ICP, ideal sales motion, FAQ
• Process docs — how we do annual planning, postmortems, retros

AI in Docs#

• Ask SpaceChat to find an answer across the entire Docs tree.
• Ask it to keep a Doc up-to-date based on recent changes ("update the on-call playbook with last week's incidents").
• Use an Agent to monitor for stale Docs (no edits in 90 days) and surface them for review.

Tips#

• Treat Docs as durable. If a Doc is changing every day, it's probably a Page in disguise.
• Snapshots are useful before any major rewrite — you can always roll back.
• Link Docs to the Tasks, Workflows, and Agents that depend on them. The AI uses those edges to keep work connected to its source.