eFerns component docs

This reference library shows how the CloudCannon Astro Component Starter was extended into a structured editorial site. The goal is not novelty. The goal is a site that developers can fork, editors can trust, and judges can inspect without guessing how anything works.

The starter primitives remain intact. eFerns adds a plant data model, editorial playbooks, experiment logs, glossary terms, and a small set of custom page sections that treat content as structured information rather than decorative copy.

Recommended review order

1. Project Tour: Review how the starter is organized and where eFerns extends it.
2. Editing a Page: See how homepage assembly still uses pageSections for top-level pages.
3. Building a Page Section: Trace the three-file pattern used for every custom eFerns section.
4. Visually Edit Components: Confirm that non-developers can safely reorder and edit sections.

What to inspect

• Custom eFerns sections under Page sections → eferns
• MDX snippets used in guides
• Collection-backed detail templates for plants, guides, experiments, and glossary entries
• Tokenized theme changes that keep the starter architecture intact

Why this library exists

This project is a public-facing editorial brand, but it is also a technical proof: this is how a content-first Astro + CloudCannon build should feel when the information architecture is serious.