Make WordPress Core

WordPress Beginner

<p>WordPress 7.0, named “Armstrong,” shipped on May 20, 2026. Here’s a rundown of what’s actually in it, what it means for developers and site owners, and what got left on the cutting room floor.</p>
<h2>AI infrastructure</h2>
<p>The headline feature is a new <strong>AI Connectors screen</strong> in the admin dashboard. From one place, you can connect your site to OpenAI, Google Gemini, or Anthropic Claude by entering API keys. Under the hood, this is powered by a new WP AI Client and Abilities API — a standardized layer that lets plugins and themes tap into whichever AI provider you’ve configured.</p>
<p>For ACF PRO users specifically, ACF fields are already wired into this system via ACF 6.8’s Abilities API integration, meaning your custom fields can participate in WordPress’s AI data layer without extra work.</p>
<p>Real-time collaboration was originally planned for 7.0 but got pulled before release. It’s still in development through the Gutenberg plugin.</p>
<h2>Block editor changes</h2>
<p>Several practical additions landed in the editor:</p>
<ul>
<li><strong>Responsive visibility controls</strong> — show or hide individual blocks per device type without a plugin</li>
<li><strong>Per-block custom CSS</strong> — add CSS directly to any block from the editor</li>
<li><strong>Visual revisions</strong> — color-coded diff view for comparing content versions</li>
<li><strong>Three new blocks</strong> — Icons, Breadcrumbs, and Headings</li>
</ul>
<p>PHP-only block registration is now supported in Core, which validates an approach ACF Blocks has used for years. That said, Core’s implementation is still more limited than what ACF Blocks offers.</p>
<p>Block Bindings got an update too: bidirectional sync with ACF fields is now possible via the new datastore, which reduces the need for custom workarounds when connecting fields to block attributes.</p>
<h2>Admin UI</h2>
<p>The admin interface got a refresh with faster screen transitions and a site-wide <strong>Command Palette</strong> (Cmd/Ctrl+K), similar to what you’d find in VS Code or Notion. It’s a small thing that adds up quickly if you’re navigating between screens frequently.</p>
<h2>Accessibility</h2>
<p>7.0 ships 24 Core accessibility fixes and 16 Gutenberg fixes, all targeting WCAG 2.2 AA compliance. The practical improvements include:</p>
<ul>
<li>Media library voice control support</li>
<li>Automatic import of alt text from IPTC photo metadata</li>
<li>Color contrast fixes in the admin dashboard</li>
<li>Screen reader verbosity improvements</li>
<li>Keyboard navigation for DataViews grids</li>
<li>Forced-colors mode support</li>
<li>Gallery lightbox accessibility fixes</li>
</ul>
<p>All new features — the Icons block, Connectors screen, visual revisions — went through accessibility review before shipping.</p>
<h2>Developer changes</h2>
<ul>
<li><strong>PHP minimum raised to 7.4</strong></li>
<li>Pseudo-element support in theme.json</li>
<li>Block Selectors API</li>
<li>Font Library now available across all theme types, not just block themes</li>
<li>WP-CLI 3.0</li>
<li>Expanded DataViews and DataForms APIs</li>
<li>Interactivity API improvements</li>
</ul>
<h2>What’s broken and what’s being fixed</h2>
<p>A publishing screen bug (ticket #65286) affects the non-block editor on custom post types, even without the Classic Editor plugin installed. The team is deploying fixes through both the Classic Editor plugin (which has 9M+ active installs) and the Hotfix plugin to cover as many sites as possible.</p>
<p>WordPress 7.0.1 is planned for mid-to-late June. WordPress 7.1-alpha is already in active development.</p>
<h2>Ecosystem updates around the same time</h2>
<p>A few plugin and ecosystem changes landed around the 7.0 release worth knowing about:</p>
<ul>
<li><strong>StellarWP</strong> rebranded as <strong>Liquid Web Software</strong>, affecting GiveWP, LearnDash, Kadence, and others</li>
<li><strong>MemberPress</strong> added native direct messaging via ClubConnect</li>
<li><strong>WPConsent</strong> rolled out Google Consent Mode V2 support</li>
<li><strong>Charitable</strong> added abandoned donation recovery and new payment gateways</li>
<li><strong>WPForms</strong> launched a native Klaviyo addon</li>
<li><strong>MonsterInsights</strong> launched Charlie Chat for plain-English GA4 queries</li>
<li><strong>HelpJet</strong> offers AI-trained customer support chatbots</li>
<li><strong>Uncanny Agent</strong> brings conversational AI for site management tasks</li>
</ul>
<p>None of these are part of WordPress Core, but they reflect where the plugin ecosystem is heading alongside the new AI infrastructure in 7.0.</p>


Collections

WordPress 7.0 'Armstrong' released May 20, 2026, introducing an AI Connectors screen for integrating OpenAI, Gemini, and Claude via a new WP AI Client and Abilities API. The block editor gains responsive visibility controls, per-block custom CSS, visual revisions, and three new blocks (Icons, Breadcrumbs, Headings). A site-wide Command Palette (Cmd/Ctrl+K) lands in the admin UI. PHP minimum is raised to 7.4, and developer-facing additions include pseudo-element support in theme.json, Block Selectors API, WP-CLI 3.0, and expanded DataViews/DataForms APIs. 24 Core and 16 Gutenberg accessibility fixes target WCAG 2.2 AA compliance. Real-time collaboration was cut from this release. A known publishing screen bug affects non-block editor on custom post types; WordPress 7.0.1 is planned for mid-to-late June.

WordPress 7.0: What's new and what it means for developers

<p>Interesting direction for WordPress development</p>


<p>What in the world… php 7.4 end of life was in November 2022! Shame… shame… shame…</p>
