Loading docs page
How the main commercial systems connect inside this repo.
These systems are meant to support a commercial launch together, not as isolated add-ons:
| System | What it covers | Where to start |
|---|---|---|
| Authentication | Account access, protected routes, session-aware pages | Runtime config and auth routes |
| Billing | Checkout, subscriptions, billing portal, webhooks | Pricing flow and Stripe configuration |
| Transactional messages tied to account or billing events | Provider config and lifecycle templates | |
| SEO | Metadata, canonical URLs, sitemap, and public discovery | Public copy, route structure, and metadata helpers |
| Security | Provider secrets, request protection, and production-safe defaults | Runtime config, env management, and launch checks |
If you are only shaping the public site and docs, you can usually leave auth, billing, and email providers disabled until later.
If you are launching a SaaS product, the usual order is:
npm run lint and npm run build.