Product Knowledge

Documentation

Use the docs as an operating manual, not a brochure. Start with product understanding, then move into concrete workflows, release discipline, and troubleshooting.

Recommended Path

1. Read Overview to understand what the platform actually wires for you.

2. Use Getting Started to reach a preview and ship one safe change.

3. Once you are in day-to-day execution, move to Workspace, Local Import, and File Previews.

Build product context first

3 pages

Overview
What the platform is and how the workflow fits together.
Open
Product
Outcomes by role (PM / Business / Developers).
Open
Getting Started
Prompt → preview → production, with verification steps.
Open

Run real tasks with confidence

6 pages

Workspace Guide
Where to go in the Project workspace (Chat, Deploy, Pay, Analytics).
Open
Use Cases
Playbooks: prompts + acceptance criteria for common products.
Open
Integrations
GitHub/Auth/Payments/Analytics: setup and verification.
Open
FAQ
Troubleshooting by symptom.
Open
Local Import
How zip import works, what gets auto-detected, and how to avoid bad archives.
Open
File Previews
What the in-app viewer can render, edit, or download across text and binary files.
Open

Understand architecture and release mechanics

3 pages

Architecture
Environments, promotion model, and failure modes.
Open
API
OpenAPI, auth, errors, pagination, webhooks.
Open
Roadmap
Now / Next priorities (subject to change).
Open

Billing, refund, and legal guidance

3 pages

Pricing & Plans
Plan selection guidance and billing expectations.
Open
Refund and Dispute Policy
Refund/dispute process and timelines.
Open
Legal and Export Restrictions
Compliance and export restrictions (high-level).
Open