Gutenberg 22.5 just dropped, and while the changelog might look like the usual biweekly polish, there are a few architectural wins I have been waiting for. If you have ever felt like you were fighting the editor just to add a simple style or maintain image proportions on a hero section, this update is specifically for you.
As we march toward WordPress 7.0, the focus is shifting from “adding things” to “making things work correctly.” Therefore, seeing refinements like native block CSS and viewport-based visibility stabilization is a breath of fresh air for those of us maintaining complex client sites. Furthermore, it follows the trend of cleaning up code we saw in Gutenberg 22.1.
Gutenberg 22.5: Native Custom CSS for Individual Blocks
The biggest technical win in Gutenberg 22.5 is the support for custom CSS on individual block instances. Previously, if you wanted to tweak a specific block without affecting every other block of the same type, you had to add a custom HTML class, save, and then go to your global stylesheet or the Site Editor. It was a fragmented workflow.
Now, the editor adds a has-custom-css class automatically. Specifically, this class is applied in both the editor and the frontend for dynamic blocks. It keeps your styles scoped and manageable. This is a massive improvement over the “wrapper block” hacks we used to employ just to change a margin or a specific border-radius.
/* How Gutenberg 22.5 handles scoped block styles */
.wp-block-paragraph.has-custom-css {
background: linear-gradient(to right, #f0f, #00f);
padding: 2rem;
border-radius: 12px;
}Aspect Ratio Control for Wide and Full Alignment
I honestly thought I had seen every way a hero section could break on mobile. Typically, when you set an image to “Wide” or “Full” width, the aspect ratio controls would vanish, leaving you at the mercy of the image’s original dimensions. Consequently, this led to massive layout shifts or awkward vertical images taking up three screens of height.
Gutenberg 22.5 finally fixes this limitation. You can now lock in your proportions (like 16:9 or 21:9) even when using wide alignments. This ensures consistent design across all screen sizes without needing custom CSS workarounds. If you missed the previous update on pattern overrides, you should check out the Gutenberg 22.4 breakdown for more context on how these features are coming together.
List View Improvements: UX That Actually Works
Navigating complex documents used to be a guessing game. The List View would show “List Item” or “Paragraph” twenty times in a row. In this release, List Items now display their actual content in the List View. Therefore, you can finally tell your sections apart at a glance. It is a small change that saves minutes of clicking around every single hour.
Other Technical Highlights
- Focal Point for Fixed Backgrounds: You can finally set a focal point on the Cover block even when using parallax/fixed backgrounds.
- Paragraph Columns: Native text column support is now baked into the Paragraph block via block supports.
- Submenu States: A new toggle allows you to keep submenus permanently expanded in the Navigation block.
Look, if this Gutenberg 22.5 stuff is eating up your dev hours, let me handle it. I’ve been wrestling with WordPress since the 4.x days.
The Takeaway
The Gutenberg 22.5 update is about stability and workflow. By integrating CSS directly at the block level and fixing alignment inconsistencies, the core team is making the editor more predictable. Specifically, the stabilization of viewport-based block visibility means we are getting closer to a truly “What You See Is What You Get” experience for responsive design. Don’t wait for WordPress 7.0 to start testing these—get into the plugin now.
