DatoCMS Content Modeling

Principles for designing structured content in DatoCMS that's reusable, editor-friendly, and survives redesigns. This skill answers "how should I model X?" — not "how do I create the model?".

When to apply

• New project content model layout
• Model vs block decisions
• Choosing single_block, rich_text, structured_text for block fields
• Reusable model link vs embedded block
• Taxonomy design: categories, tags, hierarchies, facets
• Refactor page-shaped, redesign-fragile, duplication-heavy schemas
• Diagnose record-size/block-count/nesting-depth limits; design around locale-multiplied block volume
• Admin UI organization: Content tab menu (editors), Schema tab menu (devs), saved views via item_type_filter
• Model behavior/presentation config: singleton, sortable, tree, draft-mode, all-locales-required; presentation_title_field vs title_field; collection_appearance; ordering
• Field config: validators, appearance choices (string_select+enum, framed vs frameless single_block, link_select vs link_embed); editor parameters (slug auto-fill, structured_text nodes/marks, SEO previews, required_alt_title)

Core principles