Gutenberg 15.6 Introduces Experimental Details Block and Command Center for Site Editor

Gutenberg 15.6 is now available with a new Details block tucked under the Experiments menu. Once enabled, it can be used to toggle the visibility of hidden content. This can be useful for presenting things like text transcripts for video blocks or simple spoiler alerts. By default the toggle is open in the block editor but closed on the front end. This is the first iteration, so the behavior of the toggle is still somewhat rough.

Another interesting experiment that shipped in version 15.6 is a command center for the Site Editor. It was created to be a quick search for jumping to other pages or templates in the editor.

“This can be seen as a start on an extensible command and quick search component that can be used for way-finding (go to About pageedit Archive template) and running commands (toggle top toolbar; etc),” Gutenberg lead architect Matias Ventura said in the ticket outlining the feature. “The first milestone is to power quick search for content and templates within the site editor.”

Gutenberg engineer Riad Benguella said his goal with the initial PR is to build the APIs and components for the command center but not necessarily implement all the commands. Ultimately he aims for this feature to do the following:

  • The command center can be loaded in any WPAdmin page
  • The commands and the command center are independent: Commands can be registered dynamically depending on the context
  • Some small hierarchy of commands to be able to organize the items
  • Allowing dynamic searches for commands

Gutenberg contributors are still considering how to organize and display commands better based on context, which is one reason why this feature remains behind the Experiments flag.

Version 15.6 also brings spacing presets to the Spacer block settings, allowing theme authors to create sensible presets and users to adjust spacing in a way that will look good across devices.

“Since the introduction of spacing presets, it became clear from community feedback that spacing presets should also be available for the Height control in the Spacer block,” WordPress developer advocate Birgit Pauli-Haack said in the release post. “This enhancement in 15.6 gives theme developers much more flexibility over how spacing is applied throughout a site and enables fluid Spacer blocks.”

WordPress core contributor Nick Diego filmed a short video about spacing presets for the Spacer block, which demonstrates how fluid spacing work to help a site’s content and design adapt better to different viewports.

A few other highlights in Gutenberg 15.6 include the following:

  • Adds border support to the Cover block
  • Makes Style Variations accessible in Browse Mode
  • List View now allows dragging underneath collapsed non-empty container blocks
  • Smoother animations for Drop Zone in the canvas

Check out the changelog to see all the enhancements, bug fixes, and performance and tooling updates.


8 responses to “Gutenberg 15.6 Introduces Experimental Details Block and Command Center for Site Editor”

  1. The command centre brings real value in terms of workflow. I’m impressed that we are seeing this in WP. We need more workflow feature like this to make it the block editor and FSE a better user experience.

    Other features like the option to turn off the editor in posts and just have custom fields for pure data entry use cases would also be welcome.

  2. I am happy that the new Details Block is being tested. I think it’s a useful block addition, I have tried ‘Details’ and for me it’s ok.
    In fact, I developed a similar block myself. Find it here: You can find more blocks in the block directory.
    Nevertheless, the ‘Details’ block name is confusing. I understand than ‘More’ can not be used, but for me it’s more meaningful something in the line of ‘Hide and Show’ or ‘Toggle’. Even Accordion,
    Anyway, I think ‘Details’ it’s useful and I like it.

  3. Note. this is not a comment but a message. I’ve had several comment censored for no apparent reason
    Going forward Im screen shotting all my comments as a record

    Free as in speech is your motto and that means publishing things A8 does not like. I do not expect this comment to be published but I do expect an improvement.

    • Thoughtful criticism is fine and encouraged, but when you try to comment about contributions to open source projects being “stupidly conceived” and “worse than a waste of time” you aren’t helping anyone. Screenshot away, I still won’t approve any comments that are insulting to contributors. We’re trying to have respectful discourse here. You can do better.

      • That is quoting me out of context, my opinion is that the direction that Gutenberg is going is harmful to the broader WordPress community and a great waste.

        I’m going to continue to make that case, and if you continue to censor it I will expose that fact widely

        Your motto is about “free as in speech”, I urge you not to be hypocrites

  4. I think the Block Editor is brilliant. Its one of the world’s best page builders.

    That said, it should have been a plugin or a seperate project entirely. Its such a shame it is being forced on everyone as “WordPress”. I think its so clear that this was the wrong decision, yet Gutenberg developers are stuck extremely deep in a sunken cost fallacy.

    The real heroes here are the maintainers of the Classic Editor plugin.

      • Though I only use the block editor sparingly and, it falls short for certain use cases, I agree that it should be in core because in many ways it’s a big improvement over the Classic editor which has been showing its age for a long time.

        That said the way it was implemented as default, requiring a plug-in to re-instate the older editor was wrong, when one can use a simple line of code in child theme’s functions file or other custom plug-in. A simple switch in settings would have sufficed for this and wouldn’t have put the wind up those who still needed to use the old editor. Then again “putting the wind up users” may have been a deliberate move.


Subscribe Via Email

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

%d bloggers like this: