Documentation
How to use the template — getting started, configuration, deployment, and each module
Last updated November 2, 2026
This documentation describes a deployable SaaS starter: a TanStack Start application on the Cloudflare Workers runtime, plus auth, payments, email, and other modules that are switched on or off. The docs ship with the code, so they never drift from the implementation.
Where to start
- Getting Started — one line from clone to production, including
pnpm run init.
- Configuration — site name, logo, and module switches live in one file.
- Environment — the two-layer env model and who owns each variable.
- Cloudflare — domains, secrets, variables, and automated deploys.
Map of the docs
| Group | Covers |
|---|---|
| Start | From clone to a running site |
| Config | Site configuration, navigation, and environment variables |
| Deploy | Cloudflare, D1, storage, and cache |
| Features | Integrations, auth, email, newsletter, payments, notifications, analytics, API keys, and user management |
| Develop | Project structure, design system, forms, and testing |
Conventions
- Commands always start with
pnpm; the scripts live inpackage.json. - Configuration files keep stable locations:
src/config/website.ts(site config),
src/config/products.ts (pricing plans), wrangler.jsonc (deployment and bindings), and .env (local environment variables).
- Amounts live only in the provider's price catalog — the code never keeps a second copy.