Got something worth sharing? We want to hear from you.Share Your Knowledge →

How to Test WordPress Suggestion Mode in Playground

Listening to ArticlePlaying
0%
Test WordPress Suggestion Mode in Playground before WordPress 7.2 ships

WordPress 7.2 is due on December 8, 2026, and one feature in the lineup changes how editorial teams review drafts: Suggestion Mode. Instead of waiting for Release Candidate 1 on November 17 to see it, you can test WordPress Suggestion Mode in Playground today, directly in your browser, with no local install. This guide walks through the exact steps to load the combined test build, try every suggestion type the feature supports, and judge whether it fits your own editorial workflow before it ships. I will also flag where the feature is still unsettled, because testing an in-progress build is different from testing a finished one.

What WordPress Suggestion Mode Actually Changes in the Editor

Suggestion Mode builds on Notes, the block-level commenting feature WordPress shipped in version 6.9. Notes let someone attach a comment to a specific block without touching the content itself. Suggestion Mode goes further: a reviewer can type directly into a post, and instead of overwriting the existing text, the edit appears as a highlighted marker that the author can accept or reject, as DreamHost’s rundown of the 7.2 roadmap describes it.

The feature covers more than plain text. Based on the behavior documented in the Gutenberg tracking issue for Suggest mode, it handles:

  • Typed additions, repeated backspace deletions, and pasted text, each wrapped in its own marker
  • Formatting toggles such as bold, italic, and links, each captured as a single format marker
  • Structural changes: inserting, removing, or moving blocks
  • Attribute changes, such as a text-alignment switch, which stays invisible until the author accepts it

Every suggestion ties back to a Note in the sidebar, and with more than one reviewer active, each person’s markers get a distinct tint tied to their data-author attribute. That detail matters for newsrooms and agencies where two editors might suggest changes on the same paragraph without realizing it.

The overview of WordPress 7.2’s full feature set covers Suggestion Mode alongside the new Ipsum default theme and the credential hardening work. This guide narrows in on one piece: actually trying it yourself, hands-on, before it lands in a stable release.

The reason this matters beyond curiosity is simple. WordPress sites that run any kind of editorial process, agencies with client sign-off steps, membership sites with volunteer copy editors, documentation teams working in a shared post queue, currently route that review through outside tools: Google Docs for the draft, then a manual copy-paste into WordPress once everyone signs off. Suggestion Mode is an attempt to collapse that into one place. Whether it actually holds up under real editorial load is exactly what hands-on testing is for.

Why Test WordPress Suggestion Mode in Playground Right Now

Suggestion Mode is not a settings toggle you flip on a live site. As of today, it ships only inside Gutenberg development builds, and WordPress core’s own 7.2 release schedule shows Release Candidate 1 landing November 17, with the final release set for December 8. Beta 5, the last beta before RC1, went out November 10.

That timing matters for a specific reason. The Roadmap to 7.2 post on Make WordPress Core calls Suggestion Mode the centerpiece of this release cycle, but it also warns that items on the roadmap aren’t guaranteed to ship. The feature is built from nine separate pull requests still working through review. If the team can’t merge all nine cleanly before the RC1 freeze, Suggestion Mode slips to WordPress 7.3, while smaller Notes improvements like emoji reactions could still ship on schedule.

I usually recommend testing a feature like this before it reaches RC1, not after. Once a feature freezes into a release candidate, the window for reporting a usability problem that actually gets fixed before launch narrows fast. Testing now, while the feature is still in active development, gives your feedback somewhere to land, and it also means you are not blindsided by a workflow change the week a client-facing team depends on your WordPress install.

ADVERTISEMENT

There is a second, more practical reason to test WordPress Suggestion Mode in Playground rather than waiting: Playground throws the environment away the moment you close the tab. Nothing you type gets saved to a database you have to clean up later, and nothing you break can affect a real site. That makes it a safe place to push the feature past its comfortable paths, long paragraphs, nested lists, mixed formatting, the kind of content a changelog screenshot never shows.

Step-by-Step: How to Test WordPress Suggestion Mode in Playground

WordPress Playground runs a full WordPress instance inside your browser using WebAssembly, so nothing touches your actual site or server. Here is how to load the specific build that bundles Suggestion Mode end to end.

Step 1: Open the Combined Suggest Mode Test Build

Go to playground.wordpress.net/gutenberg.html?pr=78994. This loads Gutenberg pull request #78994, which the Gutenberg team built specifically for testing. Rather than making you flip an experimental setting, this branch turns Suggestion Mode on by default, so you land straight in a working editor. Give it a few seconds; Playground compiles the WordPress environment in your browser on first load.

Step 2: Load or Create a Multi-Paragraph Post

Open an existing sample post, or write a new one with at least three or four paragraphs. The PR’s own notes call this out specifically: some of the input handling around suggestions only shows up once a post has more than one block, so a single short paragraph will hide real behavior from you.

Step 3: Switch the Post Into Suggest Mode

Click the Options menu (the vertical three-dot icon, sometimes called the kebab menu) in the top right of the editor, then look for Mode. Switch from Edit to Suggest. No experiment panel, no feature flag; on this build it’s a direct toggle.

Step 4: Test Inline Text and Formatting Suggestions

With Suggest mode active, place your cursor inside a paragraph and start typing. The new text appears with a highlighted treatment rather than replacing anything. Delete a few words with backspace and watch a single deletion marker grow instead of the text simply vanishing. Then select a phrase and toggle bold, italic, or add a link. Each of those actions wraps the selection in its own format marker rather than applying the change outright.

Step 5: Test Structural and Attribute Suggestions

Suggestions aren’t limited to text. Try inserting a new block, removing one, or dragging a block to a new position. Then change a block-level attribute, such as text alignment or a heading level. Attribute suggestions behave differently from text ones: the actual visual change stays hidden, represented only by a small treatment bracket, until someone accepts it. That’s a deliberate design choice, since showing the new alignment before approval would make it hard to tell what changed.

Step 6: Review Suggestions From the Notes Sidebar

Open the Notes sidebar (the same panel introduced for block comments in 6.9). Every suggestion you made in steps 4 and 5 should show up here as its own note, tied to the block it touched. If the sidebar was closed when you created a suggestion, it stays closed, which is worth knowing if you expect a popup to interrupt your writing flow.

Step 7: Test Undo, Redo, and the Accept/Reject Cycle

Press Cmd+Z (or Ctrl+Z on Windows) immediately after creating a suggestion. It should withdraw the suggestion entirely, revert your change, and remove the note, rather than just undoing the last keystroke. Redo brings inline suggestions and their notes back, though the tracking issue notes that redo can’t reopen a withdrawn structural or attribute suggestion. Finally, act as the “author” reviewing someone else’s suggestion: use the accept and reject controls (shown as checkmark and cross icons in current mockups) to merge a change into the block or dismiss it outright. Accepting should fold the suggestion into regular content with no trace of the marker left behind.

ADVERTISEMENT

What Suggestion Mode Means for Editorial Teams

Once you have run through the steps above, the more useful question is not “does it work” but “does it match how my team already reviews posts.” A few patterns are worth watching for specifically.

Multi-author tinting solves a real problem: on a shared editorial calendar, two people editing the same paragraph without knowing it is a common failure mode, and giving each reviewer their own marker color at least makes the collision visible instead of silently overwriting someone’s note. Where I’d stay cautious is the accessibility angle. Color-coded markers help a sighted reviewer scanning quickly, but they do nothing for a reviewer using a screen reader unless the underlying markup also exposes who made each change, not just how it looks.

The attribute-suggestion behavior in Step 5 is also worth sitting with. Hiding a pending alignment or heading-level change until it is accepted protects the author from seeing a half-approved layout, but it also means a reviewer can’t fully preview the visual effect of their own suggestion before submitting it. For a simple text edit that’s a non-issue. For a layout-heavy landing page built from several nested blocks, it could mean more back-and-forth than a straightforward “accept” click, not less.

None of that is a reason to avoid the feature. It is a reason to test it against your own content, not just a demo post, before you tell a client or a volunteer editor that WordPress now has “track changes.”

How This Technique Works for Testing Any Gutenberg Feature

The URL pattern you just used isn’t specific to Suggestion Mode. Official Playground documentation on previewing Gutenberg development branches explains that you can load any Gutenberg pull request with ?gutenberg-pr= followed by its number, or any branch tied to a PR with ?gutenberg-branch= followed by the branch name. A WordPress core PR works the same way with ?core-pr=. Keep in mind Playground pulls the latest build artifact from GitHub Actions, so if a commit just landed and is still building, you might see code that’s a few commits behind.

This is a genuinely useful habit beyond Suggestion Mode. Our broader guide to testing plugins and themes safely in WordPress Playground covers the basics of spinning up disposable test sites; combining that with PR-specific URLs lets you preview almost anything in active Gutenberg development, months before it reaches your dashboard. I’d treat it as a standing part of a WordPress testing routine, alongside checking changelogs before you apply a core update.

FAQ: Testing WordPress Suggestion Mode Before It Ships

Will this break my live WordPress site if I try the Playground link?
No. Playground runs an isolated, in-browser copy of WordPress. Nothing you do there connects to your real site, database, or hosting account, and the whole environment disappears when you close or refresh the tab.

Do I need the Gutenberg plugin installed to test Suggestion Mode?
Not for the Playground test build. The combined PR already bundles the Gutenberg code you need. To try it on a real WordPress install later, once the feature is further along, you would install the Gutenberg plugin from WordPress.org and enable the relevant experiment, assuming it is not yet merged into core.

What happens to my test suggestions if the PR changes after I test it?
Nothing persists. Each Playground session is disposable, so there’s nothing to clean up, and a future visit to the same URL will load whatever build is current at that time, not the one you tested today.

Is Suggestion Mode the same as WordPress’s real-time collaboration project?
No, and this is a common mix-up. Real-time collaboration (multiple people editing live, with visible cursors) is a separate, longer-running effort that was pulled from WordPress 7.0. Suggestion Mode is an asynchronous review feature built on top of Notes, and the two ship on different timelines.

ADVERTISEMENT

What to Watch Before Suggestion Mode Reaches a Stable Release

A few things are worth tracking as this feature matures. First, the early feedback gathered from real-time collaboration testers flagged concerns around attribution clarity and accessibility in related Notes work, and those same concerns apply directly to Suggestion Mode’s multi-author markers. Second, this feature only affects content editing; it has nothing to do with the credential hardening also planned for 7.2, such as the safer Application Passwords defaults covered in our Application Passwords security guide, so don’t confuse the two when you brief your team. Third, once 7.2 actually lands on December 8, treat it like any other major release: read the field guide, check your plugins, and update on a staging copy first, the same approach we laid out in our step-by-step guide to the 7.1.4 security update.

Below is the current 7.2 release schedule, straight from Make WordPress Core, so you can see exactly how much runway is left before Suggestion Mode either locks in or slips to 7.3.

WordPress Suggestion Mode Playground timeline showing WordPress 7.2 beta and release candidate dates toward the December 8 release
WordPress 7.2’s beta and release candidate schedule, with today’s date marked. Source: Make WordPress Core.

Testing WordPress Suggestion Mode in Playground now costs you nothing and tells you something a changelog can’t: whether the accept and reject flow actually fits how your writers and editors already work. If it feels natural on a throwaway Playground instance, it’s worth planning around for your editorial calendar once 7.2 actually lands. If it feels clumsy, note exactly where, because the nine pull requests behind it are still open for comment, and feedback from real testing carries more weight than a general wish for the feature to work differently. I’ll be re-testing this build again once RC1 goes out on November 17, to see whether the rough edges survive the freeze.

Responses

Leave a response

Your email address will not be published. Responses are reviewed before they appear.

Join the DevByte Daily list

AI, SEO and paid media coverage in your inbox. No spam.

ADVERTISEMENT

Share This

Questions or story tips?

Contact us

Enjoyed this article?

AI, SEO and paid media coverage in your inbox. No spam.