"Decoupled Drupal: Implications, risks and changes from a business perspective"
summary
Compares fully decoupled and progressive decoupled approaches, shows real builds (a paraplegic support site, a guided product selector for u‑blox, Zurich tourism hotel finder) and the exact tech choices: React/Vue front ends, JSON:API or GraphQL back ends, and the requirement for server-side rendering for SEO and accessibility. Reports organizational costs: ongoing training across a 40‑person team, shared client investment, and roughly €250k–€350k lost in early failures while processes and contracts for API schemas mature.
AI-written summary · about
chapters (8)
- 0:00Introduction and context
- 3:10Fully vs progressive decoupled
- 7:21Fully decoupled example
- 9:30Progressive decoupled example
- 14:22Skill set changes for teams
- 19:44Project costs and investments
- 27:43Future trends and Drupal's role
- 32:48Q&A session
related talks
52mShould We Decouple?
29mDecoupling 101
30mThe Time for Decoupled Drupal is Now
39mAdventures in APIs
57mProgressively Decoupled Drupal, for everyone!
01h 04mDecoupled Drupal across the stack
01h 07mDecoupled Drupal and the Front End
54mDecoupling Patterns, Services and creating an enterprise level editorial experience