Content Modelling & Delivery — overview
Purpose: Index of content modelling reference pages and the decision framework for choosing a content shape.
Who this page is for
| Audience | Why it matters to you |
|---|---|
| All engineers | Content shape decisions precede all component work |
Choosing a content shape
| Need | Shape | Page |
|---|---|---|
| A web page authors compose | Page + components | Pages vs fragments |
| Structured data reused across channels | Content Fragment | Content Fragments & models |
| A designed block reused across pages | Experience Fragment | Experience Fragments |
| JSON for an app/SPA | Exporter / CF JSON | JSON delivery |
| Classification & discovery | Tags | Tagging taxonomy |
| Images, documents, video | DAM assets | DAM & assets |
Foundation for all of them: Content architecture principles.
The PHI worked example, distributed
- The plan page itself: page + components (hero, benefits, CTA).
- Plan data (premium, excess, benefit rows): a Content Fragment, reused by page, app and comparison tools.
- The "Why choose PHI" promo block: an Experience Fragment reused across all plan pages.
- Regulatory disclaimers: a single Content Fragment referenced everywhere — one source of truth.