WordPress 7.1 ‘Mary Lou’ Ships From WordCamp US Phoenix

🇹🇷 Türkçe: Bu yazının Türkçesini oku →

I used to love watching a print shop at four on a Friday afternoon. Everyone breathed out at once, someone poured the coffee, and the day’s proofs stopped being paperwork and started being a conversation. WordPress 7.1 shipped Wednesday night from a Phoenix stage, and it is the first release in a long while that feels engineered for that same moment: people leaning over the same thing, marking it up together.

The release is named “Mary Lou” after the jazz pianist Mary Lou Williams, whose Harlem apartment was, by all accounts, an all-hours collaborative workshop. The name is not decoration. This cycle is genuinely about editing together, styling responsively without hand-written CSS, and moving the AI-adjacent groundwork one honest step forward — not five hype steps.

I have been running the release candidates on client sandboxes for the past two weeks. I would call this a solid, ship-it, upgrade-with-confidence release, provided you keep your head about the pieces that were deliberately deferred. Here is the honest read.

What is actually new

WordPress 7.1 “Mary Lou” was released on August 19, 2026, with the launch button pressed live on stage at WordCamp US in Phoenix. Release lead Anne McCarthy credits over 800 contributors, more than 170 of them contributing for the first time, and more than 1,500 enhancements and fixes across core and the editor. Twenty-plus locales were fully translated on day one.

The headline shifts are worth naming precisely.

• Notes, upgraded into a real review tool. Rich text, @mentions, emoji reactions, and the ability to annotate a specific run of text rather than the whole block. Gutenberg 23.8 added email notifications for @mentions, written in the recipient’s own language, with a direct link back to the editor.
• Responsive block styles without hand-written CSS. The Site Editor now exposes per-viewport controls; theme.json ships default breakpoints at 480px and 782px, configurable through settings.viewport. Full API in the developer field guide.
• Pseudo-state styling in the editor. Hover, focus, focus-visible, and active are first-class for Button and Navigation Link blocks. No more theme-side CSS just to give a link a hover colour.
• Two new stable blocks: Playlist and Tabs. Playlist supports waveforms and now transforms cleanly to and from Audio; Tabs handles Home/End keyboard navigation and shows each tab’s title in the Document Overview.
• Client-side media processing. Browser-based image compression, native AVIF and HDR gain map support, and a proper media editor modal instead of the old inline crop.
• SVG Icon API. Public functions — wp_register_icon_collection(), wp_register_icon(), wp_get_icon() — with SVGs sanitised through wp_kses. Icons are finally a first-class citizen for plugin and theme developers.
• Abilities API expansion. Filterable execution lifecycle, custom validation, and a shared discovery pipeline — the plumbing that AI-agent work in WordPress will lean on for the next two years.
• Persistent admin bar across editors and an always-iframed post editor, matching the Site Editor’s isolation. Some code that reaches for the global document will need updating.
• List View performance. “Select all” on a 1,000-paragraph post went from 16.8 seconds to 0.4 seconds in Gutenberg 23.8. That is not a benchmark for its own sake — it is the difference between usable and unusable on long-form content.

Two important things did not ship in 7.1: real-time collaboration, and the React 19 upgrade. Both are deliberate. The release day process confirmed React 19 is deferred past 7.1 for compatibility reasons, though there is an experimental flag in Gutenberg Settings for the brave. Attention now shifts to WordPress 7.2, targeted around December 8–10, 2026.

Why it matters for WordPress and WooCommerce people

For agencies and site owners, the responsive-styles work quietly deletes an entire class of custom CSS from your theme. You have been writing media queries for a decade to bump padding on mobile and shrink hero type on tablet. In 7.1, the editor knows how to do that itself, and it stores the values as part of the block’s global styles. On a client project this week I removed roughly 140 lines of viewport-specific overrides and did not lose a pixel of intent. That is a maintenance dividend that will keep paying.

For editorial teams, upgraded Notes finally moves review out of email and Slack threads and back into the artefact being reviewed. The email notification hook matters more than it sounds: it closes the loop for asynchronous teams and clients who do not live inside the WordPress admin. I would not call this real-time collaboration — it is deliberately not — but it is the honest, shipped version of a workflow that most agencies have been faking with plugins and screenshots for years.

For WooCommerce shops, 7.1 pairs cleanly with the WooCommerce 11.0.1 compatibility release that already went out on August 10. Nothing here is a store-breaker. The always-iframed post editor is the one item to sanity-check on custom product-related meta boxes and third-party editor plugins.

For plugin and theme developers, the SVG Icon API and the design system tokens for the admin UI are the sleeper wins. They mean your extensions can look and feel native without you rebuilding the primitives every quarter.

What I would do (or not do) about it

Upgrade. This is a strong .1 release with a mature release-candidate cycle behind it — four RCs, hundreds of fixes between them. On managed hosting, take the update. On self-managed, run your usual staging pass: hit the block editor, hit the site editor, load a long post to test List View, and check any plugin that manipulates the post editor DOM.

Delete some CSS. Genuinely. Open your theme’s stylesheet, find the media queries you wrote to tweak block spacing per breakpoint, and start moving those settings into the editor’s new per-viewport controls. Your future self, or whoever inherits the theme, will thank you.

Do not turn on React 19 in production. The experimental flag is exactly that. Wait for a stable landing, likely in 7.2 or 7.3.

Do not build a real-time collaboration workflow yet. Notes plus email notifications plus revisions is enough for ninety percent of editorial teams. If you genuinely need concurrent multi-cursor editing right now, keep watching the RTC outreach effort and wait it out.

Look at the Abilities API. If you build for AI agents or MCP servers, 7.1 is the release where the discovery and validation surface starts to look production-ready. Read the field-guide dev notes and pin down which of your existing plugin actions could be exposed as first-class abilities.

“Mary Lou” is not a headline-grabbing release like 6.0 or 7.0 were. It is the kind of release that will still be paying you back three years from now, quietly, every time you do not have to write a media query. That is my favourite kind.