WordPress 7.0 is right around the corner, and the latest release of Gutenberg 22.9 features just dropped. At first glance, bi-weekly updates can feel like incremental noise, but if you are an architect or a custom block developer, there is a specific shift in how we handle backgrounds and UI states that you shouldn’t ignore.
I have spent years wrestling with the Block Editor’s styling engine. Specifically, trying to get a background gradient to play nice with a background image in a Group block without writing a bunch of “hacky” inline CSS or custom classes. This release finally starts to address that architectural bottleneck.
The Shift to background.gradient Support
Previously, we were often stuck using the color.gradient support. The problem? It was never designed to coexist gracefully with background images. If you wanted a gradient overlay on top of an image, you usually ended up in a CSS specificity war or a race condition where one property would overwrite the other depending on how the theme was compiled.
Furthermore, Gutenberg 22.9 introduces the background.gradient support. This is distinct from the old color gradient controls. It allows block authors to enable gradients that function independently of background images. This lays the groundwork for eventually migrating all blocks to a more unified background styling system.
{
"apiVersion": 3,
"name": "bbioon/custom-hero",
"supports": {
"background": {
"backgroundImage": true,
"gradient": true
}
}
}Consequently, you can now build complex, multi-layered backgrounds directly in the editor UI without a single line of custom SCSS. It is a win for performance and maintainability.
Command Palette and Workflow Suggestions
If you live inside the editor, you probably use the Command Palette (Cmd+K). However, until now, it was mostly a basic search tool. This release (under the “Workflow Palette” experiment) introduces organized sections for Recent commands and Suggestions.
Specifically, this matters for clients who find the Full Site Editing (FSE) experience overwhelming. Instead of digging through three levels of nested menus to find “Manage Patterns,” the editor now anticipates the next move based on context. You can enable this by navigating to WP-Admin > Gutenberg > Experiments.
A Foundation for Consistent UI: EmptyState
For those of us building custom admin dashboards or complex data views, the wordpress/ui package just got a lot better with the EmptyState component. In the past, we had to roll our own placeholder logic for empty arrays or missing data, leading to a fragmented user experience.
Therefore, this new compound component provides a standardized way to handle icons, titles, and call-to-action buttons when a section has no data. It might seem small, but it’s the difference between a “broken” feeling interface and a professional, guided experience.
If you’re still catching up on the previous release, I’d recommend checking out my breakdown of the Gutenberg 22.8 features, as the new real-time collaboration fixes in 22.9 build directly on that foundation.
Forms Block: The Return of Hidden Fields
Another “finally” moment: the experimental Forms block now supports hidden input fields. I’ve seen countless dev hours wasted trying to pass session IDs or referral tracking data through Gutenberg forms without them. Now, these appear as selectable placeholder blocks in the editor but stay invisible on the frontend, where you can configure values via the Advanced panel.
Look, if this Gutenberg 22.9 features stuff is eating up your dev hours, let me handle it. I’ve been wrestling with WordPress since the 4.x days.
Summary of the Ship
Gutenberg 22.9 is a “stable-as-she-goes” release with 131 PRs that focus heavily on refining the developer experience. While the background gradient migration is the technical highlight, the real value lies in the stability fixes for Real-Time Collaboration (RTC). We are finally seeing notes sync properly without the dreaded page refresh, which has been a persistent “race condition” nightmare in collaborative editing sessions.
For official technical specs, you should always keep the Make WordPress Core notes bookmarked. Ship it.
