Skip to content

Genesis journal

The garden as a content layer

Why Astro Content Collections are the right default for blogs, docs, case studies, and reusable content models.

1 min read
A green valley with trees and mountains

Ordered growth

The garden image is useful because it is not chaotic growth. It is cultivated. Content-heavy sites need the same care: a schema, a stable URL model, search metadata, feeds, tags, and a way to preview changes locally.

Astro Content Collections provide that structure without forcing a CMS decision. Local MDX works well for templates because it keeps the repository self-contained and easy to update through GitHub.

Schema as editorial guardrail

Every post in this demo must define a title, description, publication date, tags, author, feature flag, and image metadata. Missing data fails early instead of producing incomplete SEO tags in production.

Search and feeds

The repository exposes /api/search.json for lightweight client-side search indexes and /rss.xml for feed readers. Both are generated from the same typed content source.