content-model: website - Scope content models and module functionality #347

Outcome

Define an evidence-based content model and functionality plan for Podcasting, Journaling, Blog, Videos, Events, eBook, Website pages and FAQs.

Verified context

The repository separates editorial Markdown under content/ from UI data under src/app/data/mock/. Existing content folders cover all eight areas. scripts/journal-schema.ts already validates journal and eBook frontmatter; the investigation must evaluate and reuse existing structures rather than assume a new schema is needed.

Existing media-library modelling includes #279 and #289. Review their boundaries alongside existing editorial issues before proposing additional work.

Investigation and deliverables

1. Inventory related project issues, separating editorial production from functionality, content management and schema work.
2. Map current routes, components, data types, Markdown sources and loading/rendering behaviour. Cite paths and distinguish implemented, partial, placeholder and absent functionality.
3. Specify shared and type-specific fields, requiredness, validation, identifiers, relationships, taxonomies, media references and editorial metadata.
4. Recommend Markdown sourcing and migration, separating frontmatter, runtime data and public structured-data output.
5. Propose repository-specific frontmatter schemas, examples and validation. Distinguish website content from Agents, Skills, Instructions/Guidelines, Prompts, Reports, Tasks, Plans, Docs and Specs.
6. Evaluate the content-management approach without assuming a separate CMS product or database.
7. Produce a dependency-aware plan for shared foundations and eight proposed module epics with bounded sub-issues, reusing existing coverage.

Sources

• Repository instructions and documentation
• App code
• Markdown content
• Reference schema—evaluate, do not automatically import

Acceptance criteria

• Evidence-linked inventory covers all eight content types and related Linear work.
• Field-level specification defines shared and type-specific structures, relationships and validation.
• Markdown sourcing, schema, migration and validation proposals include examples and unresolved decisions.
• Delivery plan proposes eight module epics and necessary sub-issues with dependencies, acceptance criteria and reuse of existing work.

Boundaries

Investigation and planning only. Do not implement changes, modify existing records or create the proposed epics and sub-issues. Those require separate exact previews and approval. Follow the repository’s Spec Kit requirements where applicable.