Modelling content for more than one screen
Why a content model built around fields rather than layouts survives a redesign, with a worked example of splitting a landing page into reusable parts.
- Content modelling
- Headless delivery
5 resources
Why a content model built around fields rather than layouts survives a redesign, with a worked example of splitting a landing page into reusable parts.
A short guide to running a CMS and a front end as separate systems: what each owns, how they talk, and where the seams tend to leak.
How a fictional publisher moved a filterable library to a headless front end while editors kept publishing throughout.
Where to cache between a CMS and a front end, how long, and how to invalidate on publish without a stale-page incident.
On-demand, time-based, and tag-based revalidation compared, with the failure modes of each written down.