Embracing Gutenberg in Existing Code
summary
Gutenberg shifts the editor from server to browser, forcing PHP logic to go through the REST API and introducing React components with Redux-style immutable state; network requests become several orders of magnitude slower and must be minimized and cached. Practical migration patterns include server-side rendering blocks to reuse existing PHP, adding a data-layer abstraction (repository) so parts can move to REST incrementally, and building reusable React widgets that also run inside non-Gutenberg meta boxes.
AI-written summary · about
chapters (15)
- 0:00Introduction and speaker intro
- 1:06Target audience and Gutenberg overview
- 2:14Architectural shifts with Gutenberg
- 3:19Client-side editing paradigm
- 5:52REST API and data exchange
- 11:00React components and modularity
- 13:24Redux data flow explained
- 18:53Gradual migration strategies
- 20:39Server-side rendering approach
- 25:19Data layer abstraction
- 30:56REST API integration on server
- 32:44Cross-platform compatibility
- 37:23Codebase flexibility and future-proofing
- 38:05Embracing new user experience
- 38:50Q&A session
