On May 8, 2026 — twelve days before WordPress 7.0 shipped — Matt Mullenweg pulled real-time collaborative editing from the release. The reasons were not dramatic. Race conditions. Memory efficiency problems. Bugs that only showed up under concurrent load. The kind of issues that never appear in a single-developer test environment and always appear when eleven editors touch the same product page on launch day. WordPress 7.0 went out on May 20 without it, and the AI Client became the headline feature instead.
Seven weeks later, the feature is back. WordPress 7.1 is set for August 19, 2026, and collaborative editing is the stated focus. But this time the project is doing something different: instead of quietly merging code and hoping beta testers find the edge cases, the core team launched a dedicated outreach program on June 3, explicitly asking for real teams on real hosts to test the feature in production-like conditions. The program runs through a dedicated #collaborative-editing-outreach channel on the Make WordPress Slack and stays open until the dry run on August 18.
What changed between 7.0 and 7.1
The Gutenberg 23.3 release notes, published the same day as the outreach announcement, confirm two things that matter. First, block-level notes — the comments system that did ship in 7.0 — now sync between collaborative editors without requiring a page refresh. That sounds small. It is not. In the previous build, if two editors were looking at the same post and one left a comment, the other had to reload to see it. That is the kind of friction that makes editors open a Slack channel instead of using the in-editor comments, and once they are in Slack, the in-editor system is dead.
Second, error recovery has been hardened against the cascading memory failures that plagued the 7.0 builds. The original pull request cited "recurring bugs found through fuzz testing" as one of the reasons for removal. Fuzz testing is automated stress testing — you throw garbage inputs at the system and watch what breaks. The fact that the team found these problems through fuzz testing rather than through user reports means the bugs were in the deep plumbing, not the surface. Fixing them before the outreach program starts is the right sequencing.
The scope of what "collaborative editing" means in 7.1 is also worth calibrating. The roadmap, published June 19 by annezazu, lists real-time collaboration alongside Notes features (suggestion mode and emoji reactions), a new Guidelines feature for encoding editorial rules, and responsive styling improvements. The real-time piece is the flashiest, but the Notes and Guidelines features are the ones that will actually change daily workflows for content teams. Suggestion mode means an editor can propose a change without committing it — the same "suggesting" paradigm that Google Docs made standard. Emoji reactions on comments are a small thing that reduces the friction of asynchronous feedback. Nobody needs to type "looks good" when a thumbs-up does the same job.
What the outreach program actually asks for
The call for volunteers targets "early adopters across a spread of hosting environments." That means nonprofits, small businesses, marketers, designers, and newsrooms — not just developers with self-hosted staging sites. The hosting team published a matching call on the same day, asking hosts to help surface concurrent-edit issues in customer environments and to make sure customers can run the latest Gutenberg plugin.
This is a meaningful shift in how WordPress tests features. Historically, the beta testing pool has been heavily developer-weighted. Developers test for correctness — does the API return the right value, does the block render properly. Editorial teams test for usability — can two people edit without losing work, does the presence indicator update fast enough, does the suggestion workflow feel natural. The outreach program is explicitly asking for the second type of feedback.
The testing window runs from now through August 18. Beta 1 is targeted for July 15, Release Candidate 1 for August 5. Real-time collaboration ships through the Gutenberg plugin during the cycle, not bundled into core — which means the team can iterate without holding the entire release hostage to one feature. If you want to participate, install the latest Gutenberg plugin on a test site, open the same post in two browser windows, and start editing. The Slack channel is where you report what breaks.
Why this matters more than the AI features
WordPress 7.0 shipped the AI Client, the Abilities API, and a Connectors framework for plugging in OpenAI, Anthropic, and Google. Those are infrastructure features. They matter for plugin developers building AI-powered tools, and they will shape the WordPress ecosystem over the next two years. But for the average content team — the one that runs a WooCommerce store, a news site, or a multi-author blog — collaborative editing is the feature that directly affects how many hours they spend coordinating.
The current state of multi-editor workflows on WordPress is a stack of workarounds. Post locking so two people do not overwrite each other. A third-party comments plugin for feedback. A custom revisions diff tool for tracking changes. A Slack channel nailed on top to coordinate who edits what. That stack works. It is also expensive in human attention. When two editors collide on a long product page, somebody loses thirty minutes of work and somebody else writes the apology email.
Native collaborative editing does not need to be Google Docs. It needs to be good enough that editors stop opening a second tool to coordinate. Presence indicators, live cursors, suggestion mode, and comments that sync without a refresh — that is the minimum viable feature set. WordPress 7.1 appears to be targeting exactly that minimum, which is the right call. Better to ship a stable, useful version in 7.1 than to chase feature parity with Google Docs and ship another pulled feature in 7.2.
What to do right now
If you run a WordPress site with more than one editor, three things.
First, install the latest Gutenberg plugin on a staging site and test collaborative editing today. Do not wait for 7.1 to ship. The outreach program exists because the team needs feedback from real environments, and the earlier you find a problem, the more likely it gets fixed before August 19.
Second, audit your current editorial workflow. Where do your editors coordinate? Slack? Email? A shared Google Doc that gets pasted into WordPress? Map those handoff points. When collaborative editing lands, those handoff points become unnecessary — but only if your editors know the new workflow exists and actually use it.
Third, watch the Gutenberg plugin changelog between now and Beta 1 on July 15. The real-time collaboration features are shipping incrementally through the plugin, not in one big merge. If you test once and assume the results hold for two months, you will miss improvements — and regressions.
WordPress 7.1 is six weeks away. The feature that was supposed to ship in 7.0 is finally getting the testing it needed. Whether it actually ships on August 19 depends on what happens in the next ten weeks. If you have opinions about how WordPress should handle collaborative editing, now is the time to use them.
Sources: Roadmap to 7.1 — Make WordPress Core, June 19, 2026. Collaborative Editing Outreach for 7.1 — Make WordPress Core, June 3, 2026. RTC Removed from 7.0 — Make WordPress Core, May 8, 2026. WordPress 7.0 Field Guide — Make WordPress Core, May 14, 2026.