Content Modeling for Information Architecture

Description

Maps the content types, attributes and relationships a system manages, creating a semantic model of the domain that underpins navigation, CMS structure and reuse.

A content model describes what kinds of things exist in a domain (for example recipes, ingredients, chefs, techniques), what attributes each has, and how they relate. Unlike a sitemap, which shows navigation, a content model shows the underlying semantic structure from which navigation, templates, search and APIs can be derived. The research side of content modelling grounds the model in user mental models and domain language, using interviews, card sorts and content audits, rather than in organisational silos. Rigour comes from defining each type and attribute precisely, testing the model against real content and user tasks, and validating that the relationships support the journeys users need. The BBC's work on programmes and food showed how a domain model enables pages, links and reuse at scale.

Attributes

Loss type
Latent
Effort
Weeks

Steps

  1. Step 1: Inventory all content types (pages, components, objects) in the system.
  2. Step 2: For each type, list attributes (what properties does each instance have?).
  3. Step 3: Map relationships between types (one-to-many, many-to-many).
  4. Step 4: Validate with users: do the content types match users' mental models? (Card sort or open labeling task).
  5. Mismatches between the content model and users' mental models = IA problems.

Sources

  • Everyday Information Architecture — Lisa Maria Martin
  • Designing Connected Content (Carrie Hane & Mike Atherton)

Related talks

Also known as

  • Content modelling
  • Domain modelling
  • Structured content modelling

Categories

  • Content
  • Information Architecture & Content