Use the docs as an operating manual, not a brochure. Start with product understanding, then move into concrete workflows, release discipline, and troubleshooting.
1. Complete Getting Started and ship one verifiable change.
2. Read Core Concepts to understand projects, workspaces, runtimes, and sessions.
3. For local development, continue with CLI and Public Expose.
4 pages
6 pages
9 pages
1 page
2 pages
2 pages
4 pages