Using Node.js and React with Drupal CMS at Edutopia
summary
Edutopia builds a decoupled site using Node.js + React front end with Drupal 8 as a jsonapi content service, and reports it works in production. Key pieces: a custom URL resolver endpoint that maps legacy slugs to component types, a preview flow that returns revision IDs via a jsonapi normalizer, and a media microservice on S3 + CloudFront + Lambda that generates responsive crops on demand. Redux stores API results to create a snappy UX; performance goals start at 4s on 3G with a sub‑second stretch.
AI-written summary · about
chapters (20)
- 0:00Intro
- 1:12Our Journey
- 1:49Challenges we faced
- 2:13What path would you choose?
- 3:34Is using Drupal this way supported?
- 4:17How to get the data out of the backend
- 5:06You might want a resolver
- 6:39Another Challenge: Previews
- 7:51Previews: The details
- 8:28Flexible Landing Pages
- 8:56Layout examples
- 10:10Editing layouts
- 10:49Responsive Images - How it works
- 11:27The Upside of Decoupling
- 12:40Performance tuning
- 14:08Creating the perception of speed
- 15:02Gotchas
- 16:17Our fear: the framework learning iceberg
- 18:12What to expect from decoupled Drupal? ++ a workable JSON API service +++ sold, predictable, fast API performance
- 23:23Final Thoughts
related talks
51mReact as a decoupled theme engine for Drupal
44m"Creating an enterprise level editorial experience for D8 using React"
57mProgressively Decoupled Drupal, for everyone!
46mAmbitious Editorial Experiences with Headless Drupal
01h 20mNextJS in Drupal workshop
40mLearning Node After a Career on Microsoft
01h 03mHeadless Drupal with Next.js
23mReact & the JAMstack