WordPress 7.0 Armstrong Ships with AI Infrastructure

WordPress 7.0 Armstrong launched on May 20, 2026, marking a significant milestone in the platform’s evolution. The release squad delivered three release candidates before the final version. However, the team removed Real-time Collaboration from the release due to technical challenges that required additional development time.

The official release post and Field Guide provide comprehensive developer notes and technical details. German-speaking users can explore the release through a Presswerk episode discussion. Additionally, an OpenChannels.fm episode is scheduled for May 26, 2026.

Work on WordPress 7.1 began immediately after the 7.0 release. Jeff Paul published a call for volunteers, with the first beta scheduled for July 15, 2026. The final release targets August 19, 2026, coinciding with the last day of WordCamp US.

Three New APIs Transform Plugin Development

Justin Nealey from GoDaddy explains why WordPress 7.0’s three new APIs matter more than headline features. The Connectors API enables site owners to manage AI provider keys centrally. This creates a more streamlined approach to AI integration across WordPress sites.

WP AI Client offers a single provider-agnostic call to invoke any model. This eliminates the need for developers to write separate code for different AI providers. The unified approach simplifies plugin development significantly.

The Abilities API transforms plugins from destinations users visit into actions the site’s AI agent performs autonomously. Therefore, plugins become more integrated into the overall WordPress experience. This represents a fundamental shift in how users interact with WordPress functionality.

Real-Time Collaboration Postponed

Ronak Vanpariya published a five-point technical analysis explaining why Real-Time Collaboration was pulled from WordPress 7.0. The feature faced challenges across every corner of the Site Editor. Simultaneous edits triggered race conditions that corrupted block data.

The feature’s reliance on persistent server connections would have overwhelmed shared hosting environments. Memory bloat on older devices created additional problems. Recurring block-tree breakage discovered through fuzz testing sealed the decision to postpone the feature.

Real-Time Collaboration continues development in the Gutenberg plugin. This allows the team to refine the feature before bringing it to WordPress Core. The approach prioritizes stability and performance over rushing features to release.

Content-Only Pattern Editing Arrives

Mike McAlister released a video walkthrough covering WordPress 7.0 features. Content-only pattern editing stands out as particularly impactful for site builders. This feature allows editors to modify pattern content without changing structure.

Customizable mobile menu overlays provide greater design flexibility. Block visibility controls enable responsive design without custom code. Per-block custom CSS gives developers fine-grained styling control.

Visual revisions make tracking changes easier. The new Icon and Breadcrumbs blocks expand design options. An upgraded Font Library screen simplifies typography management across sites.

WordPress 7.1 Tracking Issues Emerge

Several tracking issues for WordPress 7.1 have already been opened. Issue #76525 tracks new and enhanced block supports, carrying over items descoped from 7.0. Aaron Robertshaw maintains this as a living issue that updates as supports are added or removed.

Issue #75707 focuses on block visibility with configurable breakpoints and theme.json integration. The goal is letting themes define custom breakpoints via theme.json. This extends the visibility work introduced in WordPress 7.0.

Issue #76045 tracks continued iteration on DataViews, DataForm, and the Field API. Key work includes migrating @wordpress/dataviews to new Design System primitives. Issue #77199 covers Block Bindings integration with Block Fields and removing the previous Block Bindings UI.

Gutenberg Plugin 23.2 Released

Paulo Trentin, serving as first-time release lead, brought users Gutenberg 23.2 on May 21. The release introduces tablet and phone styling options in Global Styles. Therefore, designs now adapt automatically to each screen size.

Pop-up dialogs slide up from the bottom on mobile devices. This improves one-handed usability significantly. Animations across the editor share a consistent feel, creating a more polished experience.

Content Types management becomes smoother. Shortcode handling is more user-friendly. Revisions diff markers include clearer accessibility improvements. Real-time collaboration performs more steadily when teammates edit together.

PHP Support Policy Clarified

John Blackbourn clarified WordPress’s PHP support stance in an important post. The “beta” label for PHP 8.x support has been retired and removed retroactively from all WordPress versions. This label was discouraging hosts and developers from upgrading.

The minimum recommended version remains PHP 8.3. However, the minimum supported version is PHP 7.4. Versions 6.9 and 7.0 officially support PHP 8.5 fully.

Versions 6.8 and later fully support PHP 8.4. Versions 6.4 and later fully support PHP 8.3. This clarity helps developers and hosting providers make informed decisions about PHP upgrades.

WordPress AI Plugin Reaches 1.0

Jeffrey Paul recapped what’s new in the WordPress AI canonical plugin 1.0.0. This milestone release landed alongside WordPress 7.0. Two governance experiments stand out from this update.

Request Logging gives administrators visibility into every AI request fired across Core, plugins, and themes. Connector Approvals lets admins control which plugins can access configured AI providers. This adds important security and oversight capabilities.

Comment moderation upgrades include sentiment and toxicity sorting in the dashboard. AI alt text generation integrates into the media editor workflow. Editorial workflow terminology has been refined for clarity.

New AI Connectors Expand Options

Milind More introduced three new connectors for the WordPress AI plugin. OpenRouter provides routing across hundreds of models with cost optimization. This gives users flexibility in choosing the right model for each task.

LM Studio enables fully local inference suited to GDPR-sensitive workflows. The Universal OpenAI connector works with any OpenAI-compatible endpoint. This includes Ollama, Groq, and Mistral.

All three connectors are built on the same PHP AI Client SDK heading into WordPress Core 7.0. Therefore, setups created today carry forward without code changes after the upgrade. This ensures long-term compatibility.

WordCamp Europe Schedule Published

WordCamp Europe takes place June 4-6, 2026, in Krakow. The schedule lists 34 talks, 3 panels, 10 workshops, and 2 keynotes. This provides 49 reasons to attend the event.

A livestream will be available for remote attendees. After the event, recordings will be uploaded to YouTube and WordPressTV. This ensures global access to the content.

Notable sessions include a keynote on WordPress at CERN, an HTML API deep dive with Dennis Snell, and Navigation block changes with Sarah Norris. Matt Mullenweg delivers the closing keynote on Saturday, June 6, 2026.

WooCommerce Enables YouTube Shopping

Jay Walsh announced that WooCommerce stores can now sell directly on YouTube. The Google for WooCommerce extension version 3.6 enables this functionality. Stores connect their catalog and tag products in videos and Shorts.

Products surface as shoppable cards while viewers watch. They also appear in the Channel Shopping tab. The same Merchant Center product feed that powers Google Shopping keeps everything synchronized automatically.

AI-generated ad creative variations across formats are included. This integration opens new sales channels for WooCommerce merchants. YouTube’s massive audience becomes accessible for direct commerce.

Developer Resources Expand

Justin Tadlock rounded up what’s new for WordPress developers in May 2026. Early details on the Content Types experiment for managing custom post types emerged. A new @wordpress/grid package supports building grid-based editor UIs.

Revisions support extended to templates and patterns. A wave of block fixes covered the Tabs block, Image alignment, Search block styling, and Global Styles rendering. These improvements enhance developer capabilities significantly.

Róbert Mészáros published a guide on writing WordPress E2E tests with Playwright. The tutorial uses a book review site built on Block Bindings as the test subject. Developers learn to set up wp-env and Playwright, write dashboard tests, and verify patterns with aria snapshots.

Block Development Tools Improve

Felix Arntz demonstrated building a provider-agnostic image generation plugin using WordPress 7.0’s built-in AI Client. A single wp_ai_client_prompt() call handles provider routing. Support checks gate UI gracefully when no image-capable provider is configured.

Sérgio Santos diagnosed three specific bugs when using RichText outside a block. The format toolbar fills route to the wrong slot. The inline toolbar requires opt-in via inlineToolbar. The isSelected property never turns true outside a block context.

Each problem receives a targeted fix. The pattern has been packaged as a reusable component in 10up Block Components. This helps other developers avoid similar issues.

WordPress Starter Theme Open-Sourced

Damir Tahiri of Rareview open-sourced the WordPress starter theme underpinning the agency’s builds. The theme is Gutenberg-ready and ships with global style variables. It includes a one-command Figma sync.

An interactive setup renames and configures everything automatically. Developers can grab it on GitHub and use it as a foundation for projects. This accelerates theme development significantly.

The starter theme represents best practices accumulated through numerous client projects. Sharing it benefits the broader WordPress community. Other agencies can adapt it to their workflows.

Original Source: gutenbergtimes.com