The block editor arrived in 2018 to a divided community, and much of the criticism was earned. Years of steady releases later, Gutenberg has become something the arguments rarely acknowledge: a genuinely capable layout system built into core, fast, increasingly pleasant, and free of the shortcode archaeology that haunted the classic era.
The features that change daily editing
- Patterns: pre-built arrangements of blocks, a hero, a pricing row, a testimonial band, inserted with one click and edited in place. Registering your own patterns turns brand consistency into a menu.
- Synced patterns: edit once, update everywhere; the right home for calls-to-action and disclaimers that appear across dozens of posts.
- Block locking and content-only editing: hand clients an editable page where the layout physically cannot be broken, which quietly ends a decade of Monday-morning repair tickets.
theme.json is the adult in the room
Modern block themes centralize design decisions, palette, type scale, spacing, in a single configuration file that both the editor and the front end respect. Editors pick from your defined palette instead of a rainbow color wheel, and what they see while editing is what visitors get. For teams coming from page builders, this is the trade: slightly fewer toys, dramatically more consistency, and none of the builder's render-time overhead.
Where the lines are now
Blocks comfortably build marketing pages, posts, and landing pages that once justified a page builder license. Complex, data-driven templates still belong to your theme and custom fields, and that boundary is healthy. The practical advice for anyone who last tried Gutenberg in 2019 is simple: it is not that editor anymore, and the plugin stack you assembled to avoid it may now be the slowest thing on your site.