I’ve been watching the Gutenberg version numbers climb for years, and while some releases feel like minor polish, Gutenberg 23.0 actually addresses a few structural pain points that have been bothering developers since the FSE (Full Site Editing) rollout began. Specifically, we finally have a path toward template revisions and a way to stop legacy meta boxes from killing real-time collaboration.
The Big One: Revisions for Templates and Patterns
If you’ve ever spent three hours perfecting a Header template only to have a client accidentally delete a Group block, you know the sinking feeling of realizing there was no “undo” button once you hit save. Previously, revisions were strictly for posts and pages. In Gutenberg 23.0, this is finally changing.
The new experimental revisions panel brings the standard revision UI to templates, template parts, and patterns. This is part of the Editor Inspector: Use DataForm experiment. To test it, you’ll need to enable it under Gutenberg → Experiments. It uses the unified DataForm-based inspector, which is the direction the entire Site Editor is moving. It’s messy right now—it’s experimental for a reason—but it’s a massive step toward making the Site Editor production-ready for non-technical users.
Speaking of UI improvements, you might want to check out my previous breakdown of Gutenberg 22.9 updates to see how the interface has been evolving.
RTC and the Legacy Meta Box Problem
Real-Time Collaboration (RTC) has been the “holy grail” of the block editor, but it’s historically had a “kill switch” behavior: if the editor detected a legacy meta box, RTC was unconditionally disabled. For plugin authors, this was a bottleneck.
In Gutenberg 23.0, we now have a filterable flag, __rtc_compatible_meta_box. This allows us to tell WordPress that our meta box won’t cause race conditions during concurrent editing. You can apply this via the filter_block_editor_meta_boxes hook.
<?php
/**
* Mark a specific meta box as RTC compatible.
*/
add_filter( 'filter_block_editor_meta_boxes', function( $meta_boxes ) {
foreach ( $meta_boxes as &$meta_box ) {
if ( 'bbioon_custom_settings' === $meta_box['id'] ) {
$meta_box['__rtc_compatible_meta_box'] = true;
}
}
return $meta_boxes;
} );
Furthermore, the polling reliability has been hardened. A single corrupted sync update no longer crashes the entire poll cycle for every user in the room. If you’re working on enterprise-level sites with multiple editors, this is the stability update you’ve been waiting for since the initial RTC rollout in version 22.8.
A Technical “Gotcha”: The Guidelines Rename
We need to talk about the Guidelines experiment. If you were using it in previous versions, Gutenberg 23.0 renames everything internally. Slugs changed from content-guidelines to just guidelines. This includes the Custom Post Type (CPT) slug, REST base, and Redux store.
Because the experiment flag itself was renamed, it will likely show as disabled after you update. You’ll have to re-enable it and—more importantly—you might need to migrate your data if you were relying on those specific meta keys. It’s a classic “war story” in the making: update the plugin, lose the settings. Be careful here.
Quality of Life Refinements
- Site Identity: You can now edit Site Title and Tagline directly from the Design › Identity panel in the Site Editor. No more jumping back to Settings → General.
- Keyboard Shortcuts: Tooltips in the block toolbar now actually show the move-up/down shortcuts. It’s a small change that significantly speeds up keyboard-only workflows.
- Spacing UI: The four side inputs for padding and margin now re-order into a more logical layout when unlinked.
Look, if this Gutenberg 23.0 stuff is eating up your dev hours, let me handle it. I’ve been wrestling with WordPress since the 4.x days.
The Bottom Line
This release is a mixed bag of “finally!” (revisions) and “watch out!” (guidelines rename). While 174 PRs were merged, the focus is clearly on making the Site Editor as robust as the Post Editor. If you’re building custom blocks or handling complex client sites, start testing that __rtc_compatible_meta_box flag—it’s the future of the multi-user editing experience in WordPress.
