One-click frontends are now generated from a shared template repository — a base image, the same way every site runs the same golden CMS build. The template is a static Astro build of the CMS theme: same layout, same design tokens, pre-rendered against your content at deploy time.
Content as code
Each repository carries a seed/seed.json: a living content migration applied to your CMS on every deploy, before the build. Commit a content change, push, and the deploy publishes it — with update-on-conflict semantics, so the seed can keep evolving through the development cycle. Sensitive values never enter the repo; the seed resolves them from workflow environment variables.
Fail-soft builds
If the CMS is unreachable at build time, the build still succeeds with the identity baked into src/config.ts — a deploy never breaks because of a network blip.