Developer Docs for Evaluating the Continu Starter

These docs are for developers deciding whether the starter is worth buying, forking, or using as the baseline for a real product.

Use this site to answer the practical questions fast:

• what ships in the repo
• what kind of products the starter fits best
• how local setup, auth, billing, and access control already work
• what you will still need to customize
• how the architecture expects new features to be added

Internal runbooks, maintainer notes, and lower-level implementation docs stay in docs/dev. This surface is the buyer-facing developer documentation.

Quick Evaluation Path

1. product/starter-overview.md
2. product/what-you-get.md
3. product/vertical-fit-and-use-cases.md
4. product/implementation-paths.md
5. development/local-setup.md
6. development/integrations-matrix.md
7. development/extension-workflow.md

Evaluate

• product/starter-overview.md What the starter is for, where it is opinionated, and why the surface split matters.
• product/what-you-get.md The apps, backend package, and shared infrastructure that are already in the repo.
• product/surfaces-and-host-model.md How org, portal, and platform are separated.
• product/vertical-fit-and-use-cases.md The product shapes where this starter is strongest and where it may be too heavy.
• product/implementation-paths.md The three most realistic ways teams adopt this starter.
• product/evaluator-faq.md Short answers to the first buyer and technical-review questions.

Build

• development/local-setup.md The first-run path with continu:init, demo data, and tenant routing.
• development/evaluator-troubleshooting.md The shortest path through the setup and evaluation problems buyers hit first.
• development/auth-model.md How auth is already structured.
• development/billing-model.md How organization billing is modeled.
• development/permissions-and-capabilities.md How roles, permissions, and product gating are separated.
• development/integrations-matrix.md The fastest technical summary of what is already wired and what buyers still define.
• development/integrations-and-api.md The higher-level integration and API boundaries.

Architecture

• foundation/system-architecture.md The buyer-facing architecture summary for apps, backend, and shared packages.
• foundation/tenancy-and-routing.md How tenant routing and isolation work.
• foundation/access-control-model.md How roles, permissions, and capabilities are split.

Extend

• development/customization-guide.md Where branding, auth, billing, policies, and product rules should change.
• development/deployment-environments.md How local, preview, and production-style environments are shaped.
• development/extension-workflow.md The expected path for adding new features without fighting the architecture.

Reference

• product/release-notes-and-changelog.md The public changelog surface for buyer-visible starter changes.