Capability node
Content Modeling
Define content types, fields, and validation so content stays structured and queryable.
Why this capability exists
Structured content is the difference between a static page and a growing knowledge base. A schema makes content machine-readable and future-proof for APIs and agents.
Input
- Content types discovered during information architecture
- Examples of real content
Output
- Typed schemas for each content type
- Validation rules and required fields
- Sample entries that pass validation
Risks
- Schemas so strict they block legitimate content
- No validation, so bad data silently ships
- Modeling the current page layout instead of the content itself
Acceptance criteria
- Every content type has a schema that fails loudly on invalid data
- Adding a new entry requires no code changes
- Content renders identically in list and detail views