Documentation
Docs should explain setup, module ownership, operations, and removal paths without hiding important code boundaries.
On this page
Docs files
| File | Use |
|---|---|
| docs/launch.md | Production launch checklist. |
| docs/deployment.md | Host-agnostic deployment guide (Vercel, Netlify, Railway). |
| docs/customization.md | Branding, UI, and copy customization guide. |
| docs/development.md | Feature development workflow rules. |
| docs/architecture.md | Platform architecture boundary guidelines. |
| docs/module-removal.md | Safe module removal checklist. |
| docs/testing.md | Testing guidelines and layers. |
| docs/operations.md | Production operations, data retention, and scheduled jobs. |
| docs/billing/setup.md | Stripe and Lemon Squeezy integration guides. |
| docs/email/setup.md | Supabase Auth and Resend transactional email configurations. |
When to update docs
- Add new env vars.
- Add or change a provider setup step.
- Add a cron job or webhook.
- Change a module boundary or route map.
- Add a migration or data repair step that operators need to know.