WordPress 7.1: What Matters for Agencies

Nick d

Last time we dug into the technical side of 7.1, the iframe isolation and the developer APIs. Today I want the editorial and block building view. When it comes to what agencies actually touch every day, what landed, what got cut, and what do you test before August 19? Beta 4 just dropped with more than 114 updates and fixes, 51 in the Editor and 63 in Core.

Ido

And the headline for builders is that core now has a Tabs block. Clickable panels, with full blocks inside each one. Plus a Playlist block, plus a Table of Contents block that builds itself from your headings. That last one used to mean installing a plugin. I think that's a real shift.

Nick d

It is, but let's be careful. Does it kill the utility plugin? Core gives you the primitive. A toolkit gives you the finished control. One source we're reading, Nexter, sells a block toolkit, so it has a stake here. But its point is fair. It lists things like an accordion with FAQ schema, a dynamic repeater, and ready made presets. Core Tabs doesn't promise any of that.

Ben cohen

Here's where I get excited, though. A Table of Contents generated from headings is structure. When AI assistants read your page, they strip away the styling and the scripts and look at the skeleton. If core makes a clean heading outline the default, that's good for machines, and nobody has to remember to install anything. That's my interpretation, not something the release notes claim.

Ido

Right, and I'd push it further. The more core absorbs the basics, the more a plugin has to justify itself with something real. If your plugin is only a tabs widget, this release is a bad week for you.

Nick d

I'd disagree a little. For a simple brochure site, sure, drop the plugin. But for an agency with forty client sites, ripping out a toolkit means rebuilding every tabbed section, and nobody bills for that happily. Core plus a toolkit that matches how you build is the realistic answer. Not core versus plugin.

Ben cohen

So you're saying don't migrate for the sake of it.

Nick d

Exactly. Use core on new builds, and leave stable client sites alone until there's a reason. Now the styling side, which I think is the sleeper. Responsive styling lets you set breakpoints right in the inspector, and interactive state styling gives you hover and focus on things like buttons, without a custom stylesheet. For a lot of agencies, that's a pile of custom CSS that can finally go away.

Ido

And Beta 3 fixed something I'd have complained about. Applying a local style globally used to be all or nothing. Now the Apply globally option opens a quick review step, so you choose which modified styles go global and which stay local overrides. That's the difference between a design system and a mess.

Ben cohen

Plus the media changes. Image processing moves into the browser, with client side support for HEIC, UltraHDR, AVIF, and WebP. Infinite scroll in the Media Library by default. And Beta 3 fixed some ugly ones: long animated GIFs no longer hang, and a single HEIC upload in Safari no longer creates two entries.

Nick d

Which sounds great until your host or CDN has opinions. Browser side processing changes where the work happens, so that's a staging test, not a trust me test.

Ido

Okay, the elephant. Real time collaboration. Live editing, watching your teammate's cursor move. It was pulled from 7.0 in May, and it did not make 7.1 either.

Nick d

Per the roadmap, there are still open strategy questions, including which storage mechanism to use and whether to ship the full feature or just the underlying architecture. There's an outreach and testing effort running, but no confirmed release date. So if live co editing was your one reason to upgrade, 7.1 isn't it.

Ben cohen

I'd argue that's not a tragedy. What you get instead is a much better Notes system. Rich text formatting, @mentions that open a searchable list of collaborators, and notes on a specific text selection instead of a whole block. The roadmap also lists suggestion mode and reply notifications, though I'd treat that list as a roadmap, not a promise.

Ido

I'm less forgiving. Agencies were planning workflows around live editing. Now the process is leave a note, wait, reply. That's fine for editorial teams, but it's slower for a launch night when three people are fixing one page.

Nick d

Fair. But I'd rather have asynchronous Notes that work than live editing that corrupts a client's homepage. Deferral here looks like caution. Though I'll admit that's my read. The project simply says the approach wasn't ready.

Ben cohen

One more cut worth mentioning. Unicode email address support is not in 7.1. It's moving to a community plugin so compatibility, security, and data handling can get broader testing. For international clients, that's a wait and see.

Ido

So give me the checklist. It's August, the final is scheduled for August 19, timed with WordCamp US. What does an agency do this week?

Nick d

Here's my practical list. One, clone a client site to staging, and test it on the beta, never production. Two, check your patterns against the new responsive and state styling, especially any block level custom CSS, because overlapping rules can surprise you. Three, upload real client images, HEIC, WebP, AVIF, through your actual host and CDN pipeline. Four, confirm your theme and block plugins have a 7.1 tested release. And five, confirm you're on PHP 7.4 or higher, since that's the floor 7.0 set.

Ben cohen

And for stores and high traffic sites?

Nick d

Wait for the first point release unless your rollback process is solid. Beta 4 alone had 114 updates and fixes. It's converging, but it's still a beta.

Ido

Also remember 7.0.2 was a security release, with a REST API batch route issue among the fixes. So the update habit matters more than ever. The question is just sequencing.

Ben cohen

My takeaway? Core is eating the boring layer. Tabs, contents, hover states. The plugins that survive will be the ones doing something core won't.

Nick d

Mine is simpler. Test on staging, upgrade the small sites first, and streamline your plugin list while you're at it. If core does the job, one less plugin to maintain. See what WordCamp US announces, and we'll pick it apart after the release.