How to keep Drupal relevant in the Git-based and API-driven CMS era
summary
Keeps Drupal as the content GUI while using Gatsby build to CDN so the public site is static React bundles served from a CDN, removing PHP/MySQL from production and cutting hosting complexity. Exports content as JSON/markdown (via Drupal JSON APIs), uses Gatsby plugins to pre-process images and markdown, and fires webhook-triggered builds (Netlify/Pantheon-style) from Drupal. Handles forms and auth with serverless functions or external services, preserves Drupal content modeling and editorial workflows, and trades runtime overhead for faster pages and simpler ops.
AI-written summary · about
chapters (16)
- 0:00Intro
- 1:23Meet Usman
- 4:06Drupal as a CMS
- 6:09Decoupling the frontend
- 6:58Traditional approach
- 8:48Challenges
- 14:31Solution
- 27:31Gatsby and Drupal
- 32:01End result
- 33:24Performance
- 35:15Markdown
- 37:50Web Forms
- 40:50What is gone
- 43:06Drupal plugins
- 44:26Choose the right tool
- 51:06Drupal demo
related talks
50mUsing GatsbyJS to build a decoupled (Drupal) website (Live demo)
40mLive preview with Gatsby and decoupled Drupal
30mThe Time for Decoupled Drupal is Now
27mUnleashing the Power of Git-Based Content Management Systems
01h 01mThink Locally, Build Globally - How Drupal is powering headless omni-channel web platforms
32mThe Evolution and Future of Content Publishing
44mDemocratizing JavaScript, Jamstack, and Beyond for More Than Just Developers
27mBeyond Static: Dynamic Web Applications with Gatsby
