Content model guide

The template uses Astro content collections. Articles are dated updates. Guides are evergreen explanations. Catalog entries are structured JSON records. Taxonomies such as elements, roles, systems, and regions give the catalog browse paths and internal links. Authors provide visible accountattribute for editorial pages.

Prefer structured fields when the data will be reused. A stat, category, role, source URL, or related ID should not live only inside prose if another page needs to filter or sort by it. Keep prose for explanation and keep reusable facts in JSON.

When adding a new collection, copy an existing pattern and update src/content.config.ts, search indexing, navigation, and validation together.

Adaptation Notes

Use this guide as a working pattern, not as fixed product copy. Replace the example nouns with your project’s real terminology, then verify that each internal link still points to a generated page. If a claim depends on external evidence, attach the source in the relevant content record instead of burying it only in prose. This keeps the guide readable for users and maintainable for editors.

Before publishing, inspect the rendered page on mobile and desktop. The template is intentionally dense, so headings, cards, tables, and callouts should be checked with real text rather than short placeholders. When a section no longer applies to your niche, remove it cleanly or replace it with a more useful workflow; do not leave empty headings behind.