Exploring the new Drupal front-end with JavaScript 🌈🦄
summary
Drupal positions itself as an API‑first platform: JSON API in core is targeted for 8.6, REST exposes all entity types, and missing admin APIs are being added. A React-based administrative UI is prototyped and React admin UI work focuses on progressive decoupling while Nightwatch testing is adopted for JavaScript tests. Case studies (Weather Channel, Princess Cruises, Vodafone, MTA, New Balance) run decoupled front ends and Twitter reports an 80% page load reduction after moving initial rendering server‑side.
AI-written summary · about
chapters (7)
- 0:00Start
- 7:46In other words: A JavaScript-based client fetches the data from the API server and renders the Twitter experience
- 30:31STEPS TOWARDS A REACT UT FOR DRUPAL'S ADMINISTRATION BACKEND
- 31:04Improve our JavaScript testing infrastructure
- 32:18Create designs for the administration UI
- 33:28Allow contributed modules to use React or Twig
- 36:14Make the React UI extensible and configurable
related talks
30mThe Time for Decoupled Drupal is Now
40mFRONTEND CHOICES
21mThe Hybrid Experiment: Merging Node.js, WordPress, and React
19mJS Magic Supercharging Web Applications w/ Headless CMS and Modern frontend framework
32mWhat's Happening in the JavaScript Ecosystem?
41mPlanning a Front-end JS Application
41mYou Really Don't Need All That JavaScript I Promise
47mJavaScript
