Progressively Decoupled Drupal, for everyone!
summary
A four-person team documents a shift from failed full-headless rewrites to progressive decoupling using browser-native web components, LitElement and Open WC tooling, publishing 400+ web components across ~207 NPM packages. They show migrations that disable 60 Drupal modules, deploy a branding bar to seven sites in a week, run platform‑agnostic widgets (math, video player, upload, editable table) and build HAX as an editor and an organic static CMS that stores pages as plain HTML and works across PHP, Node or static hosts.
AI-written summary · about
chapters (13)
- 0:00Introduction and agenda
- 1:06Why progressive decoupling
- 4:55What are web components
- 10:13Government sites and web components
- 16:58Convincing teams to adopt
- 19:50Hacks editor experience
- 20:11Building and deploying components
- 25:10Progressive decoupling in practice
- 29:59Real-world web component examples
- 35:52Drupal integration and tooling
- 40:09Hax CMS and sustainability
- 47:16Future of web components
- 51:31Resources and Q&A
related talks
52m"Decoupled Drupal: Implications, risks and changes from a business perspective"
01h 04mDecoupled Drupal across the stack
01h 07mDecoupled Drupal and the Front End
01h 01mThink Locally, Build Globally - How Drupal is powering headless omni-channel web platforms
29mDecoupling 101
52mShould We Decouple?
51mDeconstructing Web frameworks for a more resilient code base
43mHow We Implemented Decoupled Drupal as Static for a Bank