With recent changes to Gutenberg, there are naming inconsistencies surrounding the Block sidebar settings.
In the ellipses drop down next to a block, there is a "Hide/Show Advanced Settings" link. Clicking on the link focuses the "Format" (formally "Block") sidebar tab.
This can cause confusion in multiple ways.
We're currently building out a (soon to be released) Gravity Forms block to allow customers to display their forms within their posts and pages with more in-depth configuration options.
Within the list of block settings, there are a group that are hidden within an "Advanced Settings" accordion. These are both settings not frequently used and attributes previously available through the Gravity Forms shortcode that need to exist for backwards compatbility. Clicking on the "Show Advanced Settings" ellipses drop down link is now taking you to a sidebar that contains another "Advanced Settings" section.
The sidebar tab name being "Format" is also confusing as none of the settings displayed in this block are formatting related; they all center around controlling the content displayed within the block.
Naming both the ellipses drop down link and the sidebar tab "Settings" or allowing developers to define both the drop down link and sidebar tabs names at the block level would resolve the confusion.
travislopes
All 3 comments
Making the labels for everything pluggable is the solution and it is something that should be done for extensibility.
Everything needs to be customizable. Plugins should be able to control their block, including what UI elements are called and their related settings.
People also use WordPress to build custom platforms and even web apps. They are going to want to be able to customize things like the labels and what things are called. The end result may not even be promoted as being WordPress. For example a hosted web site solution for restaurants. Or a hosted service for tour guide web sites. This is one of many ways that WordPress is used.
For those reasons making the labels customizable via code is something that should be possible.
carlhancock
on 11 Jan 2018
_This ticket was mentioned in Slack in #core-editor by jeffpaul. View the logs._
jeffpaul
on 26 Jan 2018
@travislopes @carlhancock Are there any remaining actionable items in this issue, or can it be closed?
danielbachhuber
on 14 May 2018
Related issues
maddisondesigns
路
3Comments
franz-josef-kaiser
路
3Comments
hedgefield
路
3Comments
davidsword
路
3Comments
moorscode
路
3Comments
Most helpful comment
Making the labels for everything pluggable is the solution and it is something that should be done for extensibility.
Everything needs to be customizable. Plugins should be able to control their block, including what UI elements are called and their related settings.
People also use WordPress to build custom platforms and even web apps. They are going to want to be able to customize things like the labels and what things are called. The end result may not even be promoted as being WordPress. For example a hosted web site solution for restaurants. Or a hosted service for tour guide web sites. This is one of many ways that WordPress is used.
For those reasons making the labels customizable via code is something that should be possible.