Content model

Content with structure.

Reusable data for people, search, systems, and agents.

View Docs Design-system model
How should website content be modeled?

Structured content model

SchemaRelationshipsMetadataStructured data

Schema-Controlled Content

Content structures define required fields, optional fields, allowed section types, validation rules, relationships, provenance, and migration metadata. TypeScript improves authoring ergonomics, but runtime validation remains mandatory because content may originate from imports, spreadsheets, APIs, or AI-assisted workflows.

Relationships

Relationships connect services, industries, locations, articles, authors, topics, case studies, media, forms, and conversion paths. These relationships drive related content, internal links, sitemaps, JSON-LD, search experiences, and agent-readable discovery.

Structured Content Example

A content object can render a page, populate metadata, generate structured data, and feed future agent APIs without duplicating meaning across unrelated files.

Service Content
{
  "template": "serviceDetail",
  "slug": "managed-site-migration",
  "title": "Managed Site Migration",
  "summary": "Move legacy website content into governed templates.",
  "relatedCapabilities": ["ingestion", "schema-validation", "quality-gates"],
  "conversionGoal": "consultation_request"
}