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 look at what the WordPress 6.9 release candidate phase changes for developers, from the string freeze to which tickets still qualify and the double sign-off needed to backport a fix.
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.
The Interactivity API: This is the big one. For years, if you wanted modern, app-like experiences on your site—like a search filter that updates results…
Why I stopped building one-off REST endpoints for a client AI integration and used the WordPress 6.9 Abilities API instead, with the code to register a single ability.
After watching a junior dev burn hours on Gutenberg boilerplate, I finally tried the AI tools for web development everyone talks about. The two that stuck were Copilot and Cursor.
A run through the small WordPress 6.9 changes that actually help developers, from a multisite fix for the News widget to term ID taxonomy templates and a new plugin requirements hook.
A client’s membership site was buried under millions of postmeta rows from a badge plugin. Moving that data to a custom table fixed the slowdown, and here’s when it’s worth doing.
WordPress 6.9 ships a Notes feature that keeps editorial feedback inside the block editor instead of scattered across Docs, Asana, and Slack. A look at how it works under the hood and where it still falls short.