tomevault-io Content Modeling Best Practices
Principles for designing structured content that's flexible, reusable, and maintainable. These concepts apply to any headless CMS but include Sanity-specific implementation notes.
When to Apply
Reference these guidelines when:
- Starting a new project and designing the content model
- Evaluating whether content should be structured or free-form
- Deciding between references and embedded content
- Planning for multi-channel content delivery
- Refactoring existing content structures
Core Principles
- Content is data, not pages — Structure content for meaning, not presentation
- Single source of truth — Avoid content duplication
- Future-proof — Design for channels that don't exist yet
- Editor-centric — Optimize for the people creating content
Resources
Start with the resource that matches the modeling decision in front of you, instead of loading every topic at once. See resources/ for detailed guidance on specific topics:
resources/separation-of-concerns.md— Separating content from presentationresources/reference-vs-embedding.md— When to use references vs embedded objectsresources/content-reuse.md— Content reuse patterns and the reuse spectrumresources/taxonomy-classification.md— Flat, hierarchical, and faceted classification
Converted and distributed by TomeVault — claim your Tome and manage your conversions.