We need to talk about the Site Editor. For a long time, the biggest complaint from serious designers was that you couldn’t get “true” responsiveness without messy CSS overrides or custom media query hacks. Gutenberg 23.2 finally goes after that directly, with an experimental feature that could change how we build themes.
I’ve spent most of a decade working with block-based layouts, and the “Responsive global block styles with states” in this release is the real deal. The update also cleans up the mobile experience and some of the collaboration logic underneath.
1. Responsive global block styles (experimental)
The headline feature of Gutenberg 23.2 is defining block styles per breakpoint right inside Global Styles. You can now switch between Tablet and Mobile states in the block settings. Font sizes are the obvious use, but the bigger deal is adaptive designs that don’t need a senior dev writing media queries for every client request.
If you read my earlier take on native block CSS fixes, you know I care a lot about clean output. This experiment moves a long way in that direction. Instead of filling the database with serialized CSS for every block instance, responsive states get handled in one central place.
2. Motion design tokens & UX polish
Animation timing is often what separates a “hacky” site from a polished one. Gutenberg 23.2 adds motion design tokens (duration and easing) to the @wordpress/theme package, which standardizes how Modals, Dialogs and Dropdowns move. The UI ends up feeling like one product instead of a pile of unrelated React components.
Speaking of Modals, they now render as bottom sheets on mobile. That’s a real accessibility improvement. People mostly browse one-handed on their phones, so putting the important actions at the bottom of the screen just makes sense. Native apps have done this for years, and now the WordPress editor does too.
/* Example of how you might utilize standardized motion tokens in your custom theme CSS */
.bbioon-custom-panel {
transition: transform var(--wp--custom--motion-duration-medium) var(--wp--custom--motion-easing-standard);
}
.bbioon-custom-panel.is-active {
transform: translateY(0);
}3. Fixing the “real-time” headache
I’ve dealt with plenty of Race Conditions in custom Woo checkouts, but collaboration in Gutenberg is a different problem. Gutenberg 23.2 includes important fixes for Real-time Collaboration (RTC), including a bug where users could end up with different titles after a refresh.
They also fixed a race condition on room creation that could split the update log. If you’ve ever had a site editor session go “out of sync,” with one dev seeing a different layout from the other, this was probably why. The update log has to be reliable before multi-user editing can become the default in WP Core.
My take
A lot of this is labeled “experimental,” but it shows where official WordPress development is going. I’d test it on staging, especially the responsive styles, to see how it plays with your existing theme.json configurations. For more on the roadmap, see my breakdown of WordPress 7.0 developer features.
If this Gutenberg 23.2 stuff is eating your dev hours, let me handle it. I’ve been working with WordPress since the 4.x days.
Other changelog highlights
- SelectControl: A new primitive added to
@wordpress/uifor consistent admin inputs. - Revisions: Diff markers now enforce a 24x24px target size for WCAG 2.5.8 compliance.
- Shortcodes: Improved transforms for
and registered shortcodes to block formats.
