You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem
I find that new users or even users with previous experience with WordPress (include builders) find hard understand and get familiar with the block concept. Change between blocks, use nesting blocks, columns, find if a block is full with or boxed and where exactly touch to modify content even with the line as soon is active (:hover) is kind of tricky. Usually require on new users more than one time or click to get on the right place. Also on the mobile view with less space on the screen and no :hover selector seems to be complicate.
Similar problems have been mentioned before, but my suggestion is more UI general on Gutenberg: #9628 (tools for selecting child/parent blocks) #6459. (Show block breadcrumbs for selected block)
Solution
Add a single line to the css: .edit-post-visual-editor .editor-block-list__block { border: dashed 1px #ccc;}provides a visual stimulus that reinforces the cognitive performance, so that the user understands a little better each block, its differences, properties and even in the future how to apply new parameters to the CSS model box or advanced functions. This feature could be activated or deactivated on the general configuration (maybe using a icon), so users who are more familiar with the experience and do not require this feature, could precind from its use (@melchoyce mentioned that this work is suggested on phase 2). On the other hand in the mobile interface it reinforces the separation of blocks or identification of them even without having the hover property of the selectors.
Screenshots with dashed lines
The text was updated successfully, but these errors were encountered:
I think better visibility and outlines on blocks is something which could be considered in phase 2. I have some concerns though over using dotted lines being a problem as a visual pattern and for some causing line movement. Let's label this for the future and take from there.
For now, I am going to close this up. We have a few issues around making the nested blocks more discoverable and I think in phase two that will improve. After that we can look at what could be next.
I personally think still the above would be a difficult visual pattern but exploring alternatives would be great.
Problem
I find that new users or even users with previous experience with WordPress (include builders) find hard understand and get familiar with the block concept. Change between blocks, use nesting blocks, columns, find if a block is full with or boxed and where exactly touch to modify content even with the line as soon is active (:hover) is kind of tricky. Usually require on new users more than one time or click to get on the right place. Also on the mobile view with less space on the screen and no :hover selector seems to be complicate.
Similar problems have been mentioned before, but my suggestion is more UI general on Gutenberg:
#9628 (tools for selecting child/parent blocks)
#6459. (Show block breadcrumbs for selected block)
Solution
Add a single line to the css: .edit-post-visual-editor .editor-block-list__block { border: dashed 1px #ccc;}provides a visual stimulus that reinforces the cognitive performance, so that the user understands a little better each block, its differences, properties and even in the future how to apply new parameters to the CSS model box or advanced functions. This feature could be activated or deactivated on the general configuration (maybe using a icon), so users who are more familiar with the experience and do not require this feature, could precind from its use (@melchoyce mentioned that this work is suggested on phase 2). On the other hand in the mobile interface it reinforces the separation of blocks or identification of them even without having the hover property of the selectors.
Screenshots with dashed lines
The text was updated successfully, but these errors were encountered: