Blog post
Launching the Template
The repo starts with a split between code-owned marketing pages and schema-backed long-form content.
The starter is built around a simple rule: not all content wants the same editing surface.
Two lanes by design
- Marketing pages stay in
.astro, where structure and presentation are tightly coupled. - Repeatable long-form content lives in
src/data/and flows through localKeystatic.
That gives the repo a stable editorial system without forcing custom landing pages into a CMS-shaped box.
Deployment stays boring
The production site is still just static files:
Astrobuilds the siteCloudflare Pagesdeploys the output fromdist/- pushes to
mainship automatically once the repo is connected
Local workflow
Run bun run dev and open /keystatic to edit the content in place. Changes write directly to the same Markdown
files
that power the site.