The fastest way to make a publication fragile is to hide product meaning in page templates. A post is not just Markdown. It has an author, a category, a set of tags, a feature state, and an image that has to work in several layouts.
Astro content collections make those rules explicit. They validate frontmatter, give route code typed data, and let components stay focused on rendering rather than guessing.
Model product decisions
The minimum useful model for a Jekflix-style publication includes:
- Posts with title, subtitle, description, author, category, tags, image, and feature state.
- Authors with a portrait, role, bio, and optional links.
- Site settings for navigation, social links, brand language, and theme tokens.
That model is small, but it is enough to drive home pages, archive pages, feeds, search data, and article metadata without duplicate configuration.
Prefer derived data
Reading time, related posts, tag indexes, and category counts should be derived at build time. The editor should not have to maintain those fields by hand unless there is a clear editorial override.
