Gutenberg 22.1 adds a tabs block and a better HTML block
Gutenberg 22.1 ships a native tabs block and an HTML block that can carry its own CSS and JavaScript. Here is what that means for custom code and how it cuts down on extra plugins.
Gutenberg 22.1 ships a native tabs block and an HTML block that can carry its own CSS and JavaScript. Here is what that means for custom code and how it cuts down on extra plugins.
WordPress 6.9 adds border radius presets to theme.json. Define a set of radius options in your theme, and content editors pick from them instead of typing arbitrary pixel values.
A client’s store had every core block loaded and a sluggish backend to show for it. Here is how we worked out which WordPress core blocks to unregister, and the snippet we used.
A client wanted their marketing team to pick which custom product attribute shows on a page, from the editor. Custom block bindings in WordPress 6.9 make that possible, and here is the source registration I used.
WordPress 6.9 fixes the parts of the Interactivity API that made SPA-like navigation painful: dynamic scripts and stylesheets load on their own, nested router regions update, and a new attachTo property can place a region anywhere.
WordPress is moving the block editor into an iframe in 6.9 and 7.0. Blocks on apiVersion 2 or lower throw warnings now and can break later. Updating to apiVersion 3 is the fix.
WordPress 6.9 overhauls how you build custom admin forms in Gutenberg. A look at the Field API, DataViews, and DataForm: more field types, rule-based validation, and reusable UI controls that cut the custom code.
A client deployed WordPress 6.9 RC1 straight to a live WooCommerce store and it broke. The fix is not a rollback, it is a real testing plan: a dedicated environment and conditional code keyed to the WordPress version.
A client’s custom site was failing accessibility checks and getting patched with inline styles and stray aria-hidden. WordPress 6.9 moves much of this into core, from screen reader notifications to live regions, so you build it in by design.
A real case from a client site: how the WordPress 6.9 heading block CSS specificity fix changed padding on custom feature boxes, and why a proper fix beats a quick override.