🇺🇸English

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

1. Content is data, not pages — Structure content for meaning, not presentation
2. Single source of truth — Avoid content duplication
3. Future-proof — Design for channels that don't exist yet
4. 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 presentation
• resources/reference-vs-embedding.md — When to use references vs embedded objects
• resources/content-reuse.md — Content reuse patterns and the reuse spectrum
• resources/taxonomy-classification.md — Flat, hierarchical, and faceted classification

Weekly Installs

1.0K

Repository

sanity-io/agent-toolkit

GitHub Stars

103

First Seen

Jan 24, 2026

Security Audits

Gen Agent Trust HubPassSocketPassSnykPass

Installed on

opencode856

codex811

gemini-cli799

github-copilot785

cursor738

kimi-cli697