{
  "id": 9434582,
  "title": "What two Contentful builds taught us about content models and publishing boundaries",
  "url": "https://urgent.news/2026/09/23/what-two-contentful-builds-taught-us-about-content-models-and",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-23T22:56:51.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/madebymonogram/what-two-contentful-builds-taught-us-about-content-models-and-publishing-boundaries-1in0"
  },
  "original_language": "en",
  "account": "Two recent Contentful projects demonstrated important lessons about content models and publishing boundaries. For the Addiction Education Society, structured content models empowered staff to update the public site independently, cutting publication time from days to minutes. In contrast, CrewAI's project required reusable page components to be mapped to Contentful models, creating a clear separation between content creation and website rendering. Both projects highlighted the importance of defining where editorial control, rendering rules, and the final publication gate reside. A headless CMS stores content separately from the code that displays it, enabling flexibility when the content model reflects what editors need while engineers maintain consistency. The projects also revealed three key questions to consider before migrating a page: what content is reusable, which system should own each publication step, and which existing systems should remain intact. AES modeled resources, stories, and core pages in Contentful, giving the team the ability to build and update pages independently. CrewAI, on the other hand, designed reusable components in Figma that mapped to structured Contentful models, allowing marketing to assemble pages while developers handled rendering through GraphQL. The distinction between these two approaches demonstrates the importance of carefully considering content modeling and publishing boundaries when migrating to a headless CMS.",
  "summary": "For Addiction Education Society (AES), we modeled resources, stories, and core pages in Contentful so staff could update the public site without developer support. The team now publishes changes in minutes rather than days. For CrewAI, we mapped reusable page components to Contentful models, then built a separate handoff that turns published Ghost articles into Contentful drafts. Both projects…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}