---
name: Content Modeling Best Practices
slug: content-modeling-best-practices
category: Frontend
description: Content Modeling Best Practices guides structured content decisions for schemas, reuse, references, and taxonomies. Use it when designing or refactoring content models in Sanity or another headless CMS.
github: "https://github.com/sanity-io/agent-toolkit/tree/main/skills/content-modeling-best-practices"
language: JavaScript
stars: 181
forks: 28
install: "npx degit https://github.com/sanity-io/agent-toolkit/tree/main/skills/content-modeling-best-practices ~/.claude/skills/content-modeling-best-practices"
installs_to: ~/.claude/skills/content-modeling-best-practices
source_path: skills/content-modeling-best-practices/SKILL.md
collection_size: 7
category_size: 705
collection_url: "https://dirskills.com/collections/sanity-io/agent-toolkit"
added: 2026-09-07T05:20:15.822Z
last_synced: 2026-09-07T05:20:15.822Z
canonical_url: "https://dirskills.com/skills/content-modeling-best-practices"
---

# Content Modeling Best Practices

Content Modeling Best Practices guides structured content decisions for schemas, reuse, references, and taxonomies. Use it when designing or refactoring content models in Sanity or another headless CMS.

**Install:**

```bash
npx degit https://github.com/sanity-io/agent-toolkit/tree/main/skills/content-modeling-best-practices ~/.claude/skills/content-modeling-best-practices
```

## README

# 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

## References

Start with the reference that matches the modeling decision in front of you, instead of loading every topic at once. See `references/` for detailed guidance on specific topics:
- `references/separation-of-concerns.md` — Separating content from presentation
- `references/reference-vs-embedding.md` — When to use references vs embedded objects
- `references/content-reuse.md` — Content reuse patterns and the reuse spectrum
- `references/taxonomy-classification.md` — Flat, hierarchical, and faceted classification