WordPress 7.0 is close now, and Gutenberg 22.9 features just landed. Bi-weekly releases usually read as incremental noise, but this one changes how backgrounds and UI states work, and if you build custom blocks that is worth ten minutes of your time.
I have spent years fighting the Block Editor’s styling engine, mostly trying to get a background gradient to sit on top of a background image in a Group block without resorting to hacky inline CSS or a pile of custom classes. This release starts to fix that properly.
The shift to background.gradient support
Until now the only real option was color.gradient, which was never designed to coexist with background images. Ask for a gradient overlay on an image and you ended up in a specificity war, or in a race where one property overwrote the other depending on how the theme was compiled.
Gutenberg 22.9 adds background.gradient, which is a separate support from the old color gradient controls. Block authors can now enable gradients that work independently of background images. It also sets up the eventual move of every block onto one unified background styling system.
{
"apiVersion": 3,
"name": "bbioon/custom-hero",
"supports": {
"background": {
"backgroundImage": true,
"gradient": true
}
}
}So you can build layered backgrounds straight from the editor UI, with no custom SCSS. Less code to compile and less code to maintain.
Command palette and workflow suggestions
If you live inside the editor you probably hit the Command Palette (Cmd+K) constantly, and until now it was a search box and not much else. Under the Workflow Palette experiment, 22.9 splits it into sections for Recent commands and Suggestions.
That matters most for clients who find Full Site Editing overwhelming. Rather than digging through three levels of nested menus to reach “Manage Patterns,” the editor guesses the next move from context. Turn it on under WP-Admin > Gutenberg > Experiments.
EmptyState, a standard placeholder
If you build custom admin dashboards or data views, the wordpress/ui package now ships an EmptyState component. Before this, everyone rolled their own placeholder logic for empty arrays and missing data, and no two looked alike.
The new compound component gives you one way to handle the icon, title and call-to-action button when a section has no data. Small change, but it is the gap between an interface that looks broken and one that tells the user what to do next.
If you are still catching up on the previous release, my breakdown of the Gutenberg 22.8 features is worth a look, since the real-time collaboration fixes in 22.9 build straight on top of it.
Hidden fields return to the Forms block
Another one of those finally moments: the experimental Forms block supports hidden input fields again. I have watched a lot of dev hours go into passing session IDs or referral tracking data through Gutenberg forms without them. They now show up as selectable placeholder blocks in the editor, stay invisible on the frontend, and take their values from the Advanced panel.
If this Gutenberg 22.9 features stuff is eating your dev hours, hand it to me. I have been wrestling with WordPress since the 4.x days.
What the release adds up to
Gutenberg 22.9 is a steady release, 131 PRs aimed mostly at the developer experience. The background gradient migration is the technical headline, but the part I care about is the stability work on Real-Time Collaboration. Notes finally sync without a page refresh, which had been a long-running race condition in collaborative editing sessions.
For the official technical detail, keep the Make WordPress Core notes bookmarked.
