I have spent a good chunk of my career cleaning up after “major” releases that broke custom checkouts, so when WordPress 7.0 “Armstrong” showed up I skipped the jazz-themed marketing and went straight for the Trac tickets. This one is more than a dashboard refresh. It puts generative AI inside Core through the new AI Client and Abilities API.
The AI Client in WordPress 7.0 and what it replaces
For years we have been bolting on custom OpenAI wrappers or loading heavy plugins to get LLM functionality into a site. WordPress 7.0 ships a provider-agnostic AI Client instead. Rather than writing separate logic for Gemini, Claude, or GPT-4, you talk to the new Abilities API, which sits in front of whichever provider is configured much like WP_Meta_Query sits in front of the database.
The new Client-Side Abilities package also covers hybrid workflows. You can fire server-side generation and manage the UI state from Javascript without the usual glue code that feels like a hack. If you are building agentic features, start here. I wrote earlier about how preparing for the 7.0 milestone forced a complete rethink of our custom adapters.
Registering blocks in PHP instead of JavaScript
Simple blocks have long carried more JS boilerplate than they deserve. WordPress 7.0 auto-registers blocks and patterns from PHP alone, so static data no longer drags you back and forth between a React component and a PHP render callback. Register the block logic once on the server and the Block API takes it from there.
<?php
/**
* Example of the new PHP-level block registration in WP 7.0
*/
function bbioon_register_armstrong_features() {
register_block_type_from_metadata( __DIR__ . '/blocks/ai-helper', [
'render_callback' => 'bbioon_render_ai_helper',
'abilities' => [ 'text-summarization', 'image-alt-suggestion' ],
]);
}
add_action( 'init', 'bbioon_register_armstrong_features' );
?>PHP minimums and breaking changes
Now the messy part. WordPress 7.0 drops support for PHP 7.2 and 7.3, and 7.4 is the new floor. If a client is still on an old server, this update will take their site down. Push them to PHP 8.3 instead, so they also get the performance work in this release. The cycle closed more than 300 bug fixes, and none of them will save you from an environment mismatch.
The Site Editor is more extensible too. The new wordpress/boot package lets us build custom admin pages that look and behave like the Block Editor, which beats the add_menu_page workarounds we have leaned on for years. The official WordPress 7.0 Field Guide has the full list of breaking changes.
Dashboard changes and responsive controls
The new dashboard looks cleaner, but the Command Palette (⌘K) is the part I use most. It works on intent rather than plain text search, so the admin stops feeling like a maze if you spend your day in a terminal. The new responsiveness controls also let you hide or reveal blocks at specific breakpoints without writing custom CSS.
If WordPress 7.0 work is eating your dev hours, I can take it on. I’ve been working with WordPress since the 4.x days.
What to do before you update
Don’t click “Update” straight on a production site. Test your Abilities API integrations on staging first, and check the server’s PHP version while you are in there. For more background, see WordPress Core AI at WCAsia 2026.
