Whitelabel
Template setup

Customization Checklist

Track the project-specific values you must replace before calling the starter production-ready.

Customization Checklist

Use this checklist before calling a new project production-ready.

Branding

  • Replace starter titles, logos, and navigation labels.
  • Update manifest identity and metadata through project.json, including the organization block that the contact page, security.txt and the structured data are built from.
  • Run pnpm run og:generate so link previews carry your name and colours.
  • Replace the example content pages with project-specific copy, and rewrite the about, contact and privacy pages so they are true of your product.
  • Rewrite the agent guidance in src/shared/content/agent-guidance.ts so llms.txt says what your product is for.
  • Keep the agent-readiness score: the "Keep the agent-readiness score" section of WHITELABEL.md lists the sources every agent-facing document is derived from.

Runtime

  • Review the local-first shell and keep only the parts your product needs.
  • Replace the example draft fields and workflow stages.
  • Add real sync behavior only if the product needs remote persistence.

Infrastructure

  • Set the Cloudflare account, database, and KV IDs in project.json.
  • Set the real domains in project.json.
  • Run pnpm run generate and create the resources named by its output.
  • Configure Google OAuth redirect URIs for local, stage, and production.

Delivery

  • Set GitHub secrets required for deploy automation.
  • Verify CI on a pull request.
  • Verify stage deploy before wiring automatic production deploys.

Related pages

Local-First WorkspaceStart with on-device drafts and optional sync so the product remains useful before backend complexity arrives.Public Content SystemPublish SSR-friendly guides and landing pages without coupling them to the authenticated app shell.Deployment PrerequisitesCreate Cloudflare resources, secrets, and domains in the right order before the first deploy.