Gutenberg 16.0 Introduces Page Management in the Site Editor

Gutenberg 16.0 was released today with page management now available inside the Site Editor. This is the first step towards a more unified experience of editing both content and design.

Users can now create new pages and view page details in the sidebar, an experience that is very similar to editing a page in the block editor except it keeps the process inside the flow of design editing.

video credit: Gutenberg 16.0 release post

“This means you can practically build out a website without leaving the Site Editor, which speeds up the site creation process, makes it easier to see what the final result will look like, and reduces the overall cognitive load of switching between editors,” Automattic-sponsored core contributor Nick Diego said.

This update to the Site Editor will be available in the upcoming WordPress 6.3 release, along with the Details block, which has been stabilized in Gutenberg 16.0 and is no longer under the Experimental flag. The implementation was scaled back to be more simple by including the summary as part of the block itself.

The Command Center, created to be an extensible quick search for jumping to other pages or templates inside the editor, has come out of the experimental stage as well in Gutenberg 16.0. This is another major feature coming to core in the next release, and its API is also now public, opening the possibility for developers to create custom commands.

A few other user-facing highlights in this release of the plugin include the following:

Check out the release post for more details on all the enhancements, bug fixes, and tooling, accessibility, and performance updates included in Gutenberg 16.0.


9 responses to “Gutenberg 16.0 Introduces Page Management in the Site Editor”

  1. Sorry to say but Gutenberg is too complicated to work with and hard to find the tools because they are hidden when not in use. Another very annoying thing is that different things flash when you move the mouse over. I use both Gutenberg and Classic. It is considerably faster to post with Classic, so I use it automatically when something is to be posted. I don’t understand Gutenberg in widget at all.

  2. I find it very strange how many high level features are added when there’s a lack of Responsive controls. Block level responsive controls are essential to any web layout and they are still absent! It would make sense if we were on year 2 of Gutenberg, but if we are adding all these high level tools then it’s baffling that responsive controls dont even have a dev assigned.

    EG: If a block has 20% padding on a large screen but on a screen smaller than 800px wide requires 10px padding – currently we need to add a class, and create the breakpoints in the theme .css file.

    It’s been mentioned since near the start of Gutenberg, and it’s just punted into the future roadmaps with no development at all.

    The lack of these controls has led to a surge of 3rd party block libraries which address that issue. But I hate to use these libs because there’s every chance they’ll be bought by a conglomerate and any site I’ve used them on will get spam bannered by the new owners: “Upgrade to RespnsivePro3 now renamed to Artherium, a Proval company”. So I avoid those solutions for fear of the sword of Damocles.

    I don’t understand how people are creating layouts for desktop and phones in Gutenberg if they can’t make block level style variations at breakpoints. It’s still a case of write it into the theme css, or worse .. into the JSON.

    • Oh good, its not just me. I decided to give blocks a chance for my latest client, and I hate so many things about it (spagetti code, chains of elements which prevent css control, it randomly making decisions about content with no way to change them), but by far the most baffling is the lack of responsive design and control. Even with core elements that have responsive options! Prime example, there’s a sidebar block which can switch between a whole bar and a dropdown, but theres no way to make it switch between them when the layout shifts to mobile!
      If I were a more competent coder, I’d build a blocks plugin that erased all the existing blocks, and replaced them with streight elements (group =

      div>, and nothing else). How anyone thinks that the current setup is a good idea is beyond me.

    • SO TRUE,
      instead of fixing missing breakpoint and responsive controls, useless features are added to gutenberg, and we stay with a “stack on mobile” checkbox on some places. Thats all it has to offer.
      No wonder elementor and co. are still so successfull.
      regards Spencer

  3. I don’t get why no professional UX designer is hired to point out the biggest issues within the interface. I’m just a user and hobby designer but some flaws are so obvious that I feel obligated to threadbomb other issues on github to raise attention for stuff I come across.

    For example the back arrow next to the heading is an obvious flaw given how the arrows work in other parts of the UI. Inconsistencies add up and the end result is what annoys users.

    It’s something that can’t be solved by the open source community and developers without spending the cash for a pro UXer. So much time is lost by the lack of priorization and discovering the UX flaws through the community. Matt if you read thise, respect the time of your devs and spend some f** bucks for a UX designer!


Subscribe Via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

%d bloggers like this: