01
Editorial clarity
TinaCMS keeps structured content in Git, with reusable blocks editors can arrange and developers can review.
A durable starting point
Fieldnote is a focused Astro starter for teams that want editorial freedom, clear application-data boundaries, and a deployment path they can explain at a glance.
One legible system
A few deliberate boundaries make the starter useful today and adaptable when the brief changes tomorrow.
01
TinaCMS keeps structured content in Git, with reusable blocks editors can arrange and developers can review.
02
Turso handles application records through one explicit, tested, fail-closed boundary.
03
Static Astro output and repository-linked Pages deployments keep the delivery model easy to inspect.
Built for a clean handoff
The starter demonstrates the important seams without turning the boilerplate into a product of its own.
Live build evidence
These rows are created by the idempotent bootstrap and fetched during the Astro build. Tina content never passes through this database.
A clear content model keeps the team moving.
Small, durable systems create useful momentum.
Notes from the field
The seeded quotes show how editorial proof can sit beside application data without confusing their ownership.
“The useful part is not another stack. It is knowing exactly where each kind of change belongs.”
Avery Chen
Product lead
“The page feels designed, but editors can still change its rhythm without asking for a deployment-sized favor.”
Mara Bell
Content designer
Your next field note
Clone the private starter, connect fresh non-production services, and make the block library your own.