Home Blog WordPress 6.9 & 7: Game changers for the Block Editor

WordPress 6.9 & 7: Game changers for the Block Editor

Jeff Chi Avatar
Illustration mit den Ziffern 6 und 7 im Blaupausen-Stil vor abstrakten Boxen und Kästen.

With the current WordPress version 6.9, a few exciting functions have been released that some users have certainly not tried out yet. These can significantly improve the way editors work with the Block Editor. WordPress 7, which is due to be released in the next weeks, will have additional groundbreaking innovations in store. We provide an overview of the most important features of both versions.

Already here: New features in WordPress 6.9

WordPress 6.9 was released at the end of last year, but some of the new features have not yet gotten the attention of all users.

Internal Notes for blocks

With the exciting new feature of Notes, internal notes can be added to blocks. This is particularly useful for teams of several people working on posts. Notes can provide useful in-editor context, for example:

  • “This headline is still WIP. Does anyone have a better idea?”
  • “Please do not delete this group. It may seem superfluous at first glance, but it is necessary for …”
  • “Which of the two options do you prefer?”
The video shows what internal Notes look like in the Block Editor.

The popular plugin Disable Comments deactivates the new Notes function by default. This is because Notes are technically WordPress comments. With the setting “Enable Certain Comment Types”, the Notes can be re-enabled.

Read more: Notes on wordpress.org

Hide blocks

An inconspicuous but practical improvement from WordPress 6.9 is the hiding of blocks. These will still appear in the block structure (list view), but not in the WYSIWYG editor and frontend. This allows complex content to be temporarily hidden and shown again later. Previously, this content would have had to be laboriously restored from revisions or saved in external text files.

A screenshot of the WordPress Block Editor displaying the "Hide" option for blocks.
Each block can be hidden using the “Hide” menu item.
A screenshot of the WordPress Block Editor showing what hidden blocks look like in the editor’s list view.
The blocks are marked accordingly in the list view.

Read more: “Hide blocks” on wordpress.org

WordPress 7: New ways of working together

The international WordPress community is currently working flat out on WordPress 7. (And we’re doing our part, too). The original release date of April 9 has intentionally been pushed back to ensure that the new functions work reliably and stable – quite some work, seeing that the new features will fundamentally improve the Block Editor.

Real-Time Collaboration

Update 08.05.2026:

The feature will not be included in WordPress 7, but will be postponed to a later version to ensure a fully robust user experience.

https://make.wordpress.org/core/2026/05/08/rtc-removed-from-7-0/

The Block Editor is being increasingly optimized for teams. This can be observed not only in the new Notes feature from WordPress 6.9, but especially in Real-Time Collaboration, which will be not much less than a real game changer.

Up until now, many users were slowed down by the fact that they could not open posts and pages in the editor that were being workend on by other team members. WordPress 7 solves this problem: Real-Time Collaboration, as it is known from other online tools, enables multiple users to work on the same post at the same time. Changes appear in real-time, and colourful cursors show which parts are currently edited by others.

The demo video shows what Real-Time Collaboration will look like.

The feature will initially be deactivated by default. Users should consider whether the new function would be useful for them and their teams and, if so, turn it on, or ask their technical contacts to do so.

More about Real-Time Collaboration:

WYSIWYG revisions

When teams work together more closely, it becomes all the more relevant to be able to track the changes. The old view for revisions may have worked well for the Classic Editor, but has reached its limits with the Block Editor. WordPress 7 brings a fundamentally revised and improved view: the changed content is displayed in the same way as it will look in the frontend. Gone are the days of users having to decipher incomprehensible HTML code.

A screenshot of the old view for revisions in the WordPress Block Editor, prior to WordPress 7.
In the view before WordPress 7, changes were only displayed as HTML code.
A screenshot of the new revisions view in WordPress 7.
The new revisions show what has been changed at first glance.

More about the new revisions:

Block Visibility

Thanks to Block Visibility, the Block Editor will finally be fully responsive. For a long time, users were tied to predefined breakpoints, for example the wrapping-point of Columns Block. With Block Visibility, editors will be able to show and hide blocks for certain viewport sizes. This allows creating customized structures for mobile, desktop and everything in between. The feature builds on “Hide Blocks”, which we already know from WordPress 6.9.

A screenshot of the WordPress Block Editor showing the "Hide Block" feature based on the viewport, for desktop, tablet and mobile.
Hide blocks at will, on desktop, tablet or mobile.

In WordPress 7, the viewport sizes will still be predefined. But already in WordPress 7.1 it will be possible to define custom sizes via theme.json.

Read more: Block Visibility on wordpress.org