The first time I tried editing a post at the same time as a client, back in the 5.x era, it fell apart into overwritten transients and lost content. Gutenberg 22.8 features a batch of changes that finally make real-time collaboration (RTC) usable for professional work. We are past plain cursor tracking now, and the editor is starting to feel closer to a shared IDE than a CMS.
I have spent years on custom block implementations and sprawling theme.json files, and this release reads as the more mature version of both. It closes interface complaints that have been open for a long time, and it hands developers a real extension point.
Real-time collaboration, past the cursor
Seeing a collaborator’s cursor helped, but it never stopped two people from typing into the same sentence. Gutenberg 22.8 adds collaborator selection highlighting: when someone else selects text, their selection appears in your editor, color coded to their avatar. Google Docs has behaved that way for years, and it takes most of the guesswork out of who is editing what in a busy newsroom.
The presence UI got a redesign as well. Your own indicator is finally visible, and a new writing preference turns collaborator notifications on or off. The stability work matters more if you run heavy editing sessions: disconnection debouncing and peer limits are what keep the editor upright when five people pile into one post.
Button states without the custom CSS
Styling hover, focus, and active states has meant custom CSS or long theme.json overrides that no client is ever going to touch. Gutenberg 22.8 adds a State dropdown to the Global Styles design panel, so those pseudo-states can be styled visually in the editor.
The change runs deeper than one panel. The Button block is the pilot, and the infrastructure underneath is built to cover the rest of the blocks later. I made the maintainability case for this in an earlier post on stopping the CSS fight for hover states.
Gutenberg 22.8 features for developers
The Connectors screen that landed in 22.7 now has an open Registry API. You can register outside providers, AI tools, CDNs, or your own internal APIs, straight into the WordPress admin. Integrations get a standard place to live instead of another settings page bolted onto the side.
// Example of using the new Connectors Registry API
import { registerConnector } from '@wordpress/connectors';
registerConnector( 'bbioon-custom-ai', {
name: 'bbioon AI Engine',
description: 'Custom processing for enterprise workflows.',
icon: 'admin-generic',
status: 'active',
settings: {
endpoint: 'https://api.bbioon.com/v1',
apiKey: '', // Masks automatically in the UI
}
} );The registry beats hand-building an options page. It sits on the native DataViews layout, so the screen matches the rest of the site editor. The official PR #76364 has the full technical breakdown.
Media performance and the admin bar
Client-side uploads now handle AVIF. AVIF compresses better, and doing the encoding in the browser keeps that load off the server. They also fixed the cross-origin isolation problem that was breaking third-party iframes, which bites anyone running heavier block extensions.
The Command Palette picked up a trigger in the admin bar, so Cmd+K works even when you are nowhere near the editor canvas. Small tweak, and it cuts a surprising amount of clicking over a week.
If keeping up with Gutenberg releases is eating your dev hours, I can take that off your plate. I have been working with WordPress since the 4.x days.
Worth testing on staging
Most of 22.8 is stability work rather than new surface. Selection highlighting in RTC and interactive state support in theme.json both close gaps that have annoyed larger WordPress builds for years. Put these Gutenberg 22.8 features on a staging site before they reach you in core, particularly if your team edits collaboratively or leans on custom styling.
My write-up of Gutenberg 22.7 and the move to RTC by default covers how the collaboration work got to this point.
