Decoupled Drupal and the Front End
summary
Explores using Drupal as a headless CMS and how front-end work changes when you bypass Drupal’s traditional theme layer. Covers concrete technologies and approaches including Drupal 8’s decoupled capabilities, JavaScript frameworks (Angular 1, Ember and the broader framework landscape), Web Components, integrating with native apps, and patterns like progressively decoupled Drupal, plus pros/cons of going headless and implications for Drupal theming.
AI-written summary · about
chapters (27)
- 0:00Intro
- 2:01Welcome!
- 2:45What we'll cover
- 3:58What is decoupled Drupal?
- 7:33Static pages
- 8:22Dynamic pages with Ajax
- 9:05Web 3.0
- 11:42The history of content management
- 13:08Rendering on the client side
- 14:05Headless or decoupled?
- 15:13Rewards of decoupled Drupal
- 18:31Risks of decoupled Drupal
- 23:11When should you decouple Drupal?
- 25:29Rewards of progressive decoupling
- 28:17Decoupled Drupal 8
- 29:55Setting up RESTful Drupal
- 32:19Testing APls with Postman
- 42:27Cross-origin requests
- 43:36Client-side frameworks
- 44:24Single-page applications
- 45:45Native mobile applications
- 48:31Drupal-aware full decoupling
- 51:30Examples of progressive decoupling
- 52:18Is Drupal at risk?
- 53:13Food for thought
- 54:15More about decoupled Drupal
- 55:49Thank you!
related talks
30mThe Time for Decoupled Drupal is Now
57mProgressively Decoupled Drupal, for everyone!
54mDecoupling Patterns, Services and creating an enterprise level editorial experience
52m"Decoupled Drupal: Implications, risks and changes from a business perspective"
52mShould We Decouple?
01h 04mDecoupled Drupal across the stack
01h 03mHeadless Drupal with Next.js
51mReact as a decoupled theme engine for Drupal