Content Modeling

Content modeling is the practice of defining the structure of your content before you start building. It answers questions like: what distinct types of content does this site have? What data does each type need? How do content types relate to each other? A content model is the blueprint (conceptually and, in Statamic, sometimes literally) for how information is organized and stored in the CMS.

In practice, a content model for a marketing site might include: a Blog post type with fields for title, author, body, featured image, category, and SEO metadata; a Case Study type with client name, industry, challenge, solution, and results; a Team Member type with name, role, bio, and headshot; and a set of Global content for navigation and site-wide settings. These types, fields, and relationships constitute the model.

The reason content modeling gets its own term is that getting it wrong is expensive. Retrofitting a poorly designed content model onto a live site — adding fields after the fact, splitting one content type into two, realizing your taxonomy structure doesn’t support the filtering you need — ranges from annoying to very disruptive. Time spent modeling upfront pays off consistently.

WordPress encourages informal content modeling, often without calling it that. You register custom post types, add ACF field groups, define taxonomies, and the model emerges. It can work fine, but there’s no formal step in the typical WordPress workflow where you sit down and think through the full structure before starting. The result is often content models that grow organically and carry some amount of technical debt.

Statamic’s architecture makes the content model more explicit. Collections, Blueprints, Fieldtypes, and Taxonomies are all configured in YAML files that live in your repository. You can see the entire content model by reading those files. That explicitness is an asset — it makes onboarding new developers easier, makes migrations more predictable, and makes it obvious when the model needs to change.

A WordPress to Statamic migration is an excellent opportunity to revisit your content model. Content that evolved without much planning often has inconsistencies — fields that exist on some post types but not others, metadata that was stored in one place for legacy reasons, taxonomy structures that don’t reflect how the site actually works. The migration guide addresses content modeling as part of the migration planning process, since migrating content without thinking through the target model tends to just move problems from one system to another.