What changes when WordPress 6.9 reaches release candidate
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.
Category: Core Updates
How WordPress 6.9 changed CSS specificity for headings
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.
WordPress 6.9 Is Coming: Here’s What Actually Matters
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…
How the WordPress 6.9 Abilities API replaces custom endpoints
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.
The small WordPress 6.9 changes that matter for developers
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.
How the WordPress Notes feature keeps feedback in the editor
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.
WordPress 6.9 is coming. Should you worry?
WordPress 6.9 RC2 is out. Here is what I test before updating client sites, the heading CSS change developers should watch, and why I wait for the .1 release.
WordPress 6.9 is fast, but is your theme?
A client’s PageSpeed score was stuck in the low 80s. WordPress 6.9 finally gives developers real control over script loading, but only if the theme uses it. Here is what changed and why the theme matters.
How WordPress 6.9 fixes email reliability
A client’s WooCommerce order emails kept landing in spam, even with SMTP set up. WordPress 6.9 fixes the deeper causes: the sender address mismatch, garbled encoding, and a 17-year-old multipart bug.
The new WordPress Abilities API, explained
A client wanted the same URL list on an admin page, a homepage block, and an external API. The old way meant duplicating logic. The WordPress Abilities API lets you define the feature once and reuse it everywhere.