I recently looked at a client site that was a mess. Their previous developer had hard-coded breadcrumbs into a header template, using logic that didn’t account for search pages or 404 errors. When the client started adding nested categories for their holiday promos, the navigation collapsed. All of that was avoidable if they hadn’t been fighting the platform.
That is why the WordPress 6.9 features that dropped this December interest me. We finally have a stabilization path for the experimental breadcrumbs block. Instead of writing custom PHP to cover paged archives or attachments, you lean on the core implementation. Building your own nav logic from scratch is rarely worth the technical debt.
What the new Abilities API replaces
The standout in this release is the Abilities API. If you’ve ever managed user permissions beyond simple roles, you know how brittle current_user_can feels once things get granular. The new API gives you a sturdier framework for registering and checking capabilities, and it is already documented in the Common APIs handbook.
I tried to build something similar for a large WooCommerce store a few years back. It was a mix of custom meta fields and some genuinely ugly filters to hide blocks from specific vendors. It worked, and it was miserable to debug once race conditions started serving stale data. With the 6.9 Abilities API back then, I would have saved about forty hours of hair-pulling.
// A simple way to check permissions using the new logic
function bbioon_check_user_ability( $user_id, $action ) {
// This is just a conceptual wrapper for the new API approach
if ( ! function_exists( 'wp_user_can_perform_action' ) ) {
return false;
}
return wp_user_can_perform_action( $user_id, 'bbioon_manage_inventory' );
}Smaller changes worth knowing about
Another time-saver: theme.json now handles pseudo-classes like hover and focus for the Button block. You no longer have to dig into CSS files or add !important just to change a button color on hover, since it is handled at the block level. The HTML block also got a modal-based makeover, so editing CSS and JS inside the editor no longer means scrolling sideways in a narrow sidebar.
The official WordPress developer news has the full breakdown of these changes. Worth reading before you start your next build.
What’s the move for 2026?
The lesson here: stop over-engineering. WordPress is moving toward a more standardized, API-driven architecture. Legacy Flash scripts are out and the @wordpress/boot package has routing support now, so the platform is shedding baggage. Stick to the core APIs and you will spend less time maintaining your own.
This stuff gets complicated fast. If you’re tired of debugging someone else’s mess and you just want your site to work, drop my team a line. We’ve probably seen it before.
