content-modeling-best-practices

Design reusable, presentation-agnostic content models across CMSs.

173|27|Updated Mar 11, 2025
One-click install
npx skills add https://github.com/sanity-io/agent-toolkit --skill content-modeling-best-practices
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: content-modeling-best-practices
Source: https://github.com/sanity-io/agent-toolkit/tree/main/skills/content-modeling-best-practices
Command: npx skills add https://github.com/sanity-io/agent-toolkit --skill content-modeling-best-practices

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Content modeling best practices help teams design content structures that are flexible, maintainable, and presentation-agnostic across CMSs. They emphasize separation of content from presentation, encourage reuse, and guide taxonomy design.

Core Features & Use Cases

  • Principle-driven guidance: separation of content from presentation, taxonomy strategies, and reuse patterns across CMSs.
  • Concrete patterns: shared components, shared fields, content fragments, taxonomy references, and governance.
  • Sanity-specific guidance: apply these patterns when modeling schemas in Sanity to ensure cross-project consistency.

Quick Start

  • Audit your current schemas to identify 2-3 candidate reusable blocks.
  • Create a small shared field set and apply it to two content types (e.g., article and author).
  • Refactor names to meaning-focused terms and align taxonomy usage to avoid duplication.

Frequently Asked Questions about content-modeling-best-practices

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is content modeling and how does it improve CMS architecture?

Content modeling structures content to be flexible and presentation-agnostic across CMSs. It separates content from presentation, encourages reuse through shared components, and guides taxonomy design to ensure maintainable schemas.

How do I design a reusable content schema in Sanity?

Design reusable content schemas by creating shared field sets and applying them to multiple content types. Refactor names to meaning-focused terms and align taxonomy usage to ensure cross-project consistency and avoid duplication.

What's the best way to structure taxonomy references in a content model?

Structure taxonomy references by aligning usage to avoid duplication and applying governance patterns. Meaning-focused naming and clear taxonomy strategies ensure content fragments remain reusable across different presentation layers.

Does this content modeling approach work across different CMSs or only for Sanity?

This approach applies to content architecture across CMSs and projects. It provides principle-driven guidance for separation of concerns and reuse patterns, with specific concrete examples for implementing these strategies when modeling schemas in Sanity.

Why should I separate content from presentation in my schema design?

Separating content from presentation ensures your structured content remains flexible and maintainable. It allows shared components and content fragments to be reused across different presentation layers without altering the underlying schema.

How do I start refactoring an existing content model for better reuse?

Start by auditing current schemas to identify reusable blocks, then create a small shared field set for two content types like article and author. Finally, refactor names to meaning-focused terms and align taxonomy usage.