A durable starting point

Make room for the story. Keep the system legible.

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

Every layer has a job.

A few deliberate boundaries make the starter useful today and adaptable when the brief changes tomorrow.

01

Editorial clarity

TinaCMS keeps structured content in Git, with reusable blocks editors can arrange and developers can review.

02

Purposeful data

Turso handles application records through one explicit, tested, fail-closed boundary.

03

Quiet operations

Static Astro output and repository-linked Pages deployments keep the delivery model easy to inspect.

Compose in sections

A page should bend without breaking.

Start with a coherent library, then add, remove, repeat, and rearrange blocks as the story evolves. Each choice stays constrained enough to protect the design.

See the authoring guide
An abstract field journal diagram showing connected content, data, and delivery layers
Content, data, and delivery stay connected without sharing ownership.

Built for a clean handoff

Small surface area. Useful proof.

The starter demonstrates the important seams without turning the boilerplate into a product of its own.

Reusable section types
7
Each backed by one Astro component.
UI frameworks
0
Public pages stay Astro-native.
Storage responsibilities
2
Editorial content and application data stay separate.
Source of deployment
1
Private GitHub main, linked directly to Pages.

Live build evidence

Representative records, read from Turso.

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.
Maya
Small, durable systems create useful momentum.
Jonah

Notes from the field

Good defaults should make future choices easier.

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

Start with a system you can explain.

Clone the private starter, connect fresh non-production services, and make the block library your own.

Review the setup guide