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.
A tiny custom post type tweak turned into a two-month project because we chased perfection instead of shipping. Why incremental development, the way WordPress 6.9 itself is built, works better.
A client outgrew their all-in-one site builder and hit a wall. Why WordPress open source gives you ownership, portability, and customization a closed platform can’t.
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 got a free five-page site through a WordPress.com Business plan deal. It works for a simple presence, but the moment you need custom PHP, API integrations, or deeper WooCommerce, you hit the limits of a managed build.
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.
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.
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.