Everything is a Block: How WordPress Rewrote the WYSIWYG
summary
WordPress replaces the old WYSIWYG with a React-based editor called Gutenberg that models every piece of content as a block, with static blocks saving normal HTML and dynamic blocks (for example a “latest posts” block) saved as a reference and re-rendered on demand. Blocks get serialized as JSON and injected into the post body field inside HTML comments, so every paragraph can become a separate block; editor features include slash autocomplete, accessibility color warnings, reusable blocks, and implications for migration and field-level data modeling.
AI-written summary · about
chapters (12)
- 0:00Introduction and speaker intro
- 1:01Concept of blocks in WordPress
- 9:23WordPress vs Drupal approach
- 15:39Gutenberg data model explained
- 21:38WordPress embracing JavaScript
- 28:45React licensing and community reaction
- 31:54Gutenberg as phase one of evolution
- 34:46Drupal community thoughts on blocks
- 37:35Data model and migration concerns
- 41:31Content personalization and caching
- 44:24JavaScript and future of components
- 47:14Backwards compatibility and adoption
