01
Compose
Shape pages from focused, reorderable sections while the design system keeps every combination coherent.
Fieldwork — Build with clear boundaries
A durable Astro starter
Small tools. Clear jobs.Better things, built to last.
A polished foundation for editorial teams who want flexible pages, honest data boundaries, and almost no browser overhead.
Clear ownership
A calmer way to compose the web.
Each layer does one job well, so editors can move quickly without turning the site into a black box.
02
Publish
Keep stories and page structure in reviewable Git-backed content with a friendly Keystatic workflow.
03
Extend
Add real application behavior through a separate Turso boundary without tangling database records into the CMS.
Structured freedom
Enough choice to feel expressive. Enough constraint to stay good.
Editors choose the story, rhythm, color tone, and arrangement. Reusable Astro components hold the accessibility, responsive behavior, and finish.
8 blocks
One ordered field. A complete, adaptable homepage with no route-level copy.
Intentionally lean
Built around the things that matter.
- 0UI framework islands
- The public page is static Astro HTML with one focused animation module.
- 8Reusable section types
- Add, duplicate, remove, and rearrange each one from the CMS.
- 3Clear content owners
- Keystatic for editorial content, Turso for application data, Astro for rendering.
From the notebook
Ideas with a little dirt on them.
Practical notes about keeping systems legible, content portable, and software pleasant to change.
View all notesSystems
Designing with boundaries
Small, legible boundaries make a starter easier to understand, test, and adapt.
Field note
Field notes from the edge
Static delivery and deliberate build-time data can be a strong, refreshingly simple combination.
Practice
The small data manifesto
Representative data should prove the integration without turning a starter into an accidental product.
Application data
A tiny guestbook, deliberately kept out of the CMS.
This build-time snapshot demonstrates where structured application records belong—and labels its source honestly.
Turso snapshot
“A calm starting point for content-rich Astro projects.”
“Git-backed stories and application data, each in the right home.”
The best starter is not the one with the most pieces. It is the one whose boundaries make the next decision obvious.
Content stays portable. Data stays purposeful. The public page stays fast.
Ready to adapt
Keep the boundaries. Change everything else.
Reorder the story, rewrite every section, or add another reusable block—the page can evolve without rebuilding its foundation.