Coupled? Decoupled? Headed? Headless? What Does it All Mean?
summary
Drupal claims it can operate as Twig and Render API coupled, JSON:API/GraphQL headless, or progressively decoupled so teams pick tradeoffs: coupled gives full CMS features and server rendering but ties to PHP/Twig and full deployments; headless/decoupled lets JavaScript front ends, needs Node hosting and custom APIs, and adds complexity most sites don’t need; progressively decoupled mixes both. Practical notes: Drupal’s Varnish and Cache API deliver static-like performance, cache invalidation is lazy, and a working decoupled search module uses Search API plus web components.
AI-written summary · about
chapters (25)
- 0:00Introduction and overview
- 1:04Understanding front end and back end
- 2:08Robot analogy and terminology
- 3:54Headed vs headless CMS
- 4:38Coupled CMS explained
- 5:42Decoupled vs truly decoupled
- 6:48Progressively decoupled approach
- 8:14Headed approach for site owners
- 10:59Headed approach for developers
- 12:22Use cases for headed approach
- 16:41Decoupled approach explained
- 22:22Decoupled approach for developers
- 26:19Benefits of decoupled front ends
- 31:59Headless CMS explained
- 33:04Headless for site owners and developers
- 35:54Use cases for headless CMS
- 36:57Progressively decoupled explained
- 38:01Progressively decoupled for site owners
- 38:42Progressively decoupled for developers
- 41:32Drupal supports all approaches
- 42:59Hosting considerations
- 44:25Bonus terms: static generation
- 46:34Bonus terms: server side rendering
- 47:16Bonus terms: incremental rebuilds
- 48:19Q&A and module showcase
