I worked with a high-traffic media site where the editorial team lived in a state of low-grade panic. About twelve authors and editors were all working across the same long-form guides. One person would delete a section thinking it was an old draft while another was still waiting for feedback on it. The feedback itself was scattered across Slack, email, and, I am not kidding, sticky notes on someone’s monitor.
My first instinct was to go heavy. I looked at enterprise-grade editorial workflow plugins that lock down posts and enforce strict states, and I thought about building a custom post-locking mechanism. That worked for about a day. Then the team started complaining they could not move fast enough. The technical “fix” was killing their productivity because it was too rigid for the way they actually worked. What they needed was better communication inside the editor, not more restrictions. That is where the new WordPress 6.9 features come in.
Solving collaboration with WordPress 6.9 features
The standout for me is block-level notes, which is exactly what my client needed. Instead of jumping into Slack to ask why a paragraph changed, editors leave threaded comments directly on the block, and the conversation stays in context. When you are 3,000 words deep in an article, having that discussion sitting next to the content saves real time. Context matters when several people have their hands in the same post.
Then there is the visibility toggle, the “Hide and Show” feature. My client used to “draft” promotional blocks by keeping them in a separate document and pasting them in when needed, which was clunky and prone to formatting errors. Now they build the block, toggle it hidden, and switch it on when the sale goes live. Nobody deletes the stashed content by accident, because it never leaves the post. It just stays invisible to readers until you are ready.
The command palette and custom actions
For those of us who live in the dashboard, the expanded Command Palette (Ctrl/Cmd + K) now works everywhere, not only in the Site Editor. The part that matters for developers is that you can register your own commands. If a client constantly needs to jump to a specific settings page or run a custom sync, you can hand them a shortcut, and that kind of small convenience is what earns their trust.
I used the Extensible Commands API to add a “Clear Custom Cache” action for a client who was tired of hunting through three sub-menus. Here is how you would register something similar with the bbioon prefix:
// Registering a custom command for the Command Palette
wp.data.dispatch( 'core/commands' ).registerCommand( {
name: 'bbioon/quick-settings-jump',
label: 'Jump to Agency Settings',
icon: 'admin-generic',
callback: () => {
window.location.href = '/wp-admin/admin.php?page=bbioon-agency-settings';
},
} );
The whole admin experience in 6.9 keeps moving toward feeling like a modern app rather than a legacy CMS. It comes down to speed and cutting the “click-debt” that piles up over years of site management.
On-demand block CSS for classic themes
Performance updates are boring right up until your site starts failing Core Web Vitals. WordPress 6.9 loads block CSS on demand for classic themes. Plenty of themes used to ship one huge stylesheet covering every block in existence even when the page used two of them. Now only what is on the page gets loaded. On sites carrying a lot of legacy code, which are the ones I usually get called in to fix, that is a free speed-up with no configuration to write.
What this changes for teams
WordPress 6.9 gives you more than a list of new blocks like the Accordion or the Math block, though both are useful for technical documentation. The bigger change is that the editor is now built for several people working on the same content. If you manage a team or a complex site, these tools are what separate a smooth launch from a chaotic one. Do not repeat my mistake and over-engineer a solution when the platform has finally shipped the tools to do it properly.
This stuff gets complicated fast. If you are tired of debugging someone else’s mess and just want your site to work, drop my team a line. We have probably seen it before.
Which of these are you rolling out for your clients first, the notes or the command palette?
