-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New feature: Using Block Guide Outlines to get a different view of the page layout. #22383
Comments
It would be interesting if it could be provoked via holding down a key or something - instead of a view you have to keep toggling on/off. Seems more of an "in the moment" thing. |
The real problem to solve here (and something we should stay focused on in regards to this issue) is that it is very difficult to select parent blocks. |
Here is a link to discussion during the Gutenberg Design Triage. I am linking in this issue: |
Potential solutions to that particular problem:
It's worth noting that #22508 in particular is very similar to the ideas proposed by this issue. |
Since this issue was opened, we made a lot of improvements to ease selecting parent blocks (parent block selector, list view, breadcrumbs....). I think we can close this issue now and we can reopen if we have new concrete proposals. |
Is your feature request related to a problem? Please describe.
In the new G2 interface it is harder to figure out the outlines of the various blocks.
It was easier before G2 as the outlines were visible when a block was selected.
(One can go to Tools (top toolbar) then select the Select icon and see the selected block outline.)
Describe the solution you'd like
The more complex layouts get for instance using columns, groups and other blocks it would be very useful to be able to turn on a general outline of all the blocks on the page. Similar to how EditorsKit uses the "Block Guide Lines".
I made a wireframe for how this could be added to Gutenberg. The one downside I see is that this View area can be crowded.
The text was updated successfully, but these errors were encountered: