Content Authoring

Locations

• Docs: content/docs/** -> routes under /docs/...
• Handbook: content/handbook/** -> routes under /handbook/...
• Blog: content/blog/** -> routes under /blog/...
• Wildlife entries: content/wildlife/**
• System updates: content/system-updates/*.json
• Record library data: src/product-data/record-library.json

Admin Portal

• Decap CMS is served from /admin.
• Local authoring is configured through local_backend: true.
• For local CMS editing, run the site and the Decap proxy together.
• Collections currently include docs, handbook, blog, recipes, wildlife, record library, and system updates.

Frontmatter

---
title: My Page
description: Optional description
date: 2025-01-01 # blog only
---

Structured Collections

Recipe Archive

• The Recipes A Taste of Home window reads from recipe entries in content/recipes/**.
• Recipes are exposed to the client through /recipes.json.
• Current recipe fields include:
  • title
  • branch
  • moods
  • aroma
  • story
  • anchor
  • ingredients
  • ritual

Record Library

• The original Record Library and Our Record Library both read from the same normalized record-library data source.
• Manual fields you can author today include:
  • album title
  • artist
  • year
  • owners
  • favorites / GOAT’d
  • discovered by
  • why it matters
  • memory note
  • relationship status
  • moods
  • tracks and optional YouTube IDs
• Visual vinyl styling is generated automatically from the album and artist seed.

System Updates

• Update Center content comes from JSON entries in content/system-updates.
• Releases can auto-open, expire, carry primary and secondary actions, and list multiple update items.

Images & Assets

• Place assets next to the MDX and reference relatively.

Reader Windows

• Deep link to a page such as /docs/intro to open it in a Reader window.
• From the desktop, open the Reader app to browse and open multiple pages.
• /docs, /handbook, and /blog are treated as Reader-managed index routes.