I recently had a client come to me with a massive WooCommerce store, about 50,000 products, complaining that their dashboard felt like it was stuck in 2012. They wanted all the shiny new toys: AI-generated product descriptions, smart media search, the works. Then I looked under the hood and found PHP 7.2 and a mountain of legacy code. I had to tell them straight that you can’t build a skyscraper on a swamp. That is why the recent WordPress 7.0 roadmap discussions matter to anyone actually building for the web.
The core committers just wrapped up their November 2025 check-in, and the message is clear: WordPress is trimming the fat. The minimum PHP version is finally jumping to 7.4. Any dev knows 7.4 has been EOL for years, but for Core this is a real win, because it means strictly typed code. Better types make the codebase legible to AI models, which is what turns the “Abilities API” from a pipe dream into something buildable. Hacking AI integration onto a loosely typed legacy PHP version is a recipe for a race condition you will never solve.
Why the WordPress 7.0 roadmap leans on AI and performance
The most interesting part of the meeting was the approach to AI. Rather than hardcoding a ChatGPT wrapper into the editor, which would be the lazy option, the project is looking at browser-based models via the W3C WebML group. The AI runs on the user’s machine, so the data stays local and your server does not melt. That means searching the media library for specific subjects, something like “show me all photos of blue suede shoes,” without shipping every image off to a third-party API. The details are in the official Make WordPress blog.
My first reaction to the “Admin Redesign” was skepticism. We have all seen redesigns that just move the cheese. The 7.0 plan is more restrained: a new coat of paint and some life brought back to WP Admin. They are looking at view transitions so the dashboard behaves like a modern app instead of a page-reloading relic from the early 2000s. They are also fixing the scary Site Health warnings, the ones where a client sees a red circle and assumes the site is about to explode. Making those actionable is a big win for anyone who supports clients daily.
/**
* Checking for Abilities API support in a custom block
* This is the kind of stuff coming in the WordPress 7.0 roadmap.
*/
function bbioon_check_ai_capabilities() {
if ( ! function_exists( 'wp_get_ai_client' ) ) {
return;
}
$client = wp_get_ai_client();
// Check if the browser-based model is available
if ( $client->has_ability( 'image-recognition' ) ) {
// Run local processing logic here
error_log( 'Local AI is ready to roll.' );
}
}
add_action( 'init', 'bbioon_check_ai_capabilities' );The release cadence is shifting too. Starting in 2026 we head back to three major releases a year, which is the right move. Lining up 6.9 with State of the Word was a fun experiment, but a predictable schedule beats a flashy one when you are the person doing the upgrades. It gives you time to test, break things and fix them before the client notices there was an update at all.
The reality of moving forward
I have spent 14 years watching people avoid updates because they are afraid of breaking things. The move to 7.0 is a different kind of update, because the changes are foundational. If you are still clinging to old PHP versions or to classic workflows that ignore the Block Editor’s newer APIs, the gap is only going to widen. The 7.0 roadmap reads like a platform turning into a proper application framework.
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.
What is your biggest headache with the current admin, the cluttered settings or the flood of notifications? Tell me whether you are actually looking forward to AI in core or bracing for more bloat.
