You write the new services page. You send it to a colleague for a look. Back comes an email with eleven changes in it, you make nine of them, they reply about the other two, and by Thursday nobody is quite sure which version is the real one. Every business with a website has lived some version of that afternoon. The WordPress editor is quietly building the thing that ends it, and the honest story of where that work has got to is more interesting than the excited one.
A comment, pinned to the sentence it is about
On Tuesday 14th October 2026, the WordPress project released Gutenberg 24.2, and its headline change is notes. If you have ever used a shared document and left a comment attached to a particular line, you already know the idea. Instead of a separate email listing changes, the remark sits in the margin beside the page, pinned to the exact block it refers to, and it stays visible while you carry on editing rather than covering what you are working on. When the screen gets narrow, each thread politely shrinks to a little circle showing whose comment it is, and a click opens it back up. There is a new Notes option in the editor’s menu to show, minimise or hide them.
It is a small, humane feature, and anyone who has approved a web page by email will recognise immediately why it is better.
Where this actually is, which is the whole point
Here is the part most coverage this month got wrong, and getting it right is why this article is worth your two minutes. Notes are in Gutenberg, not in WordPress itself. Gutenberg is the workshop where the editor is built: a separate plugin, updated every couple of weeks, used by people who want to see what is coming before it arrives. Features live and are tested there, sometimes for a long time, before any of them reach the WordPress that runs an ordinary business website.
So when does the shared, live, two-people-at-once version of this land in the WordPress you actually use? The project has given a plain answer, and it is the opposite of the hype. Real-time collaborative editing is, in the WordPress project’s own words, “intentionally not on the roadmap” for the next main release. It is being worked on in the open, carefully, and it is not being rushed into the version due this December. An article that tells you that is more use to you than one that joins in promising it.
The smaller things you might use sooner
The same release brought a handful of changes an ordinary site is more likely to meet first:
- One search for links. When you add a link in the navigation menu, the search now looks across everything at once, pages, posts, categories and tags together, each labelled by what it is, rather than making you pick the type first.
- Gallery ordering. In an image gallery you hand-pick, you can now sort by date or name and then drag the pictures into whatever order you like, with a Random option that reshuffles them on each visit.
- Duotone for more blocks. The two-tone colour effect now works on galleries, on the Media and Text block and on video, not just single images.
React 19, in one careful paragraph
One change needs a word because you may hear about it. The editor is built on a library for web and native user interfaces called React, and this release switches on the newer version, React 19, by default. Sites running a theme or plugin known not to get along with it are automatically kept on the older version, and there is a switch to turn it off. For almost every site it will make no visible difference at all. And the project has said that this newer version, too, is unlikely to fully land in the December release, which is the same unhurried honesty as the notes feature. You do not need to know anything more about React than that.
There are also two specific speed improvements to the panel you use for adding blocks. They are real and they are small, and it would be overselling them to say they make your website faster, so we will not.
Three machines for the same job
The most interesting thing the project did this month is easy to miss. Alongside the release, it published a guide asking testers to compare three different designs for the underlying machinery that a shared editing session would need, and to report back on how each one feels to work with. Three competing approaches to the same problem, built in public, handed to volunteers, with the project openly saying it wants help choosing which foundation to build on.
That is an unusual and rather admirable way to make software, and it is also why this takes time. You do not get a feature that quietly works for millions of sites by rushing the part underneath it. Most people who use WordPress have no idea this is how it is made, and it is worth knowing, because it is the reason you can trust the thing when it does arrive.
What this means for your site today
Nothing, and that is worth saying plainly, because an article about a software release gets read as a warning out of habit. Nothing has changed on your website, nothing is required of you, and there is no update to chase. This is a look through the workshop window, not a job on your list.
Where we come in
The quiet reason a managed host reads a plugin release in October is so that nothing surprising happens to your site in December. Watching what is being built, and what is deliberately being held back, is how we make sure the version that does reach your site is the boring, uneventful kind of arrival, which is the only good kind. If you are curious enough to see notes for yourself, you can install the Gutenberg plugin on a copy of your site, never the live one, and try it. And if you would rather simply get on with running your business and let someone else keep an eye on all of this, that is rather the point of being looked after.
In a year or two, the arguing about the words on your new services page will happen on the page itself, pinned to the sentence in question, instead of drifting through three days of email. It is a small, real improvement to ordinary working life, and it is being built slowly and in the open, which is exactly how you would want it done.
Related reading
- WordPress 7.2 arrives on 8th December, and the interesting part happens first
- Your host will tell you a PHP upgrade makes your site faster, and the benchmarks disagree
Sources
- What’s new in Gutenberg 24.2?, Make WordPress Core, 14th October 2026.
- What’s new for developers? (October 2026), WordPress Developer Blog, 14th October 2026.
- Real-time Collaboration: a guide to sync engines, Make WordPress Core, 14th October 2026.
