Skill

content-modeling-best-practices

General principles for structured content modeling that apply across CMSs, with Sanity-specific guidance. Use when designing content schemas, planning content architecture, or evaluating content reuse strategies.

npx claudepluginhub jadecli/jadecli-claude-plugins

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Principles for designing structured content that's flexible, reusable, and maintainable. These concepts apply to any headless CMS but include Sanity-specific implementation notes.

Supporting Assets

resources/content-reuse.mdresources/reference-vs-embedding.mdresources/separation-of-concerns.mdresources/taxonomy-classification.md

SKILL.md

Similar Skills

content-modeling-best-practices

114

Guides content modeling best practices for Sanity and headless CMSes: schema design, content architecture, reuse, references vs. embeds, separation of concerns, taxonomies. For designing or refactoring content types.

4 files

sanity

content-type-modeling

Designs content type hierarchies, reusable parts, and field compositions for headless CMS using Type > Part > Field pattern. Covers composition vs inheritance and multi-channel reusability.

6 tools

content-management-system

content-modeling

Designs author-friendly content models for AEM Edge Delivery blocks. Use when creating new blocks or changing existing ones that alter authoring structure.

2 files

aem-edge-delivery-services

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitFeb 9, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

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

See resources/ for detailed guidance on specific topics:

Separation of content and presentation

Reference vs embedding strategies

Content reuse patterns

Taxonomy and classification