-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Merge Inserter and Settings; Drag and Drop blocks from Inserter into Navigator #22319
Comments
@mariohamann This is a very interesting proposal! This is something we will need to discuss a lot closer! |
@mariohamann (I moved the inserter button to the top area just to the left of "Switch to Draft" just to have it closer to the right sidebar block screen.) How did you make your examples, Mario? |
@mariohamann Thanks for the very well described issue. I'd recommend also commenting on and adding links to your issue from related issues like #22113. One issue with the drag and drop approach is that it's not accessible to keyboard-only users like those with impaired vision. It does also seem like a long way to drag an item. I think there needs to be an option (additionally?) within block navigation itself to add blocks, which is something that has already been explored and needs some refinement: |
I went ahead and added another prototype. |
This is an awesome exploration. I think this is one of those things that will take some experimentation to get right. I left a comment on the original issue. In short, I think it might be good to start simple for now. Let's get a panel working and then ideate from there. There are several promising ideas including a floating panel and one that's tied to the right sidebar. |
@paaljoachim Excuse me for being late ..: I created them with Apple Keynote because I'm currently not in the Slack design group and therefore don't have access to the Figma files. @marceloaof Interesting idea to flip the whole thing. Personally I think that the navigator on the left side is more promising as it is more known from other applicatons (think of Google Slides etc. etc.). In fact reading from left to right is currently the approach even in WordPress admin – Admin menu on the left (= navigator and overview – "where am I?") and connected content on the right. |
@mariohamann If you join the WordPress.org slack team and send me a DM with your email, I would be happy to send you an invite. |
I apologize for opening two issues in one, but they are so closely related that they only make sense together.
Problem
1: Space problem due to current block inserter
The current trend shows that the Block/Pattern Inserter can be activated and deactivated by clicking. At the moment the inserter and the settings panel take up quite a lot of space when activated. In fact both panels are never used at the same time. You do not insert a block and set it at the same time. I also had to realize that I am often busy activating and deactivating the block inserter to get the space on the screen back (16" display).
2: Block inserter and Navigator cannot be used simultaneously.
What would be much more likely to be used simultaneously would be the Block Inserter and the Navigator Panel, so that you could drag and drop something from the Block Inserter into the Navigator Panel. This is currently not possible because both the Block Inserter and the Navigator Panel are placed on the left side, as can be seen here: #22113
Solution
Merge Block Inserter and Settings Panel
Referring to #21080 (comment) the question arises whether the block inserter might not be better placed on the right side where the settings panel is.
Floating Action Button to display the blocks
The block overview could, for example, be displayed using a floating button (hereinafter FAB). As defined in the material design, the function to insert blocks would be quite suitable for this: "Floating action buttons provide quick access to important or common actions within an app. (https://material.io/develop/android/components/floating-action-button/)
A small shadow for this button might be quite good from a usability perspective, but might not fit the current Gutenberg design.´
The question arises whether after inserting the block, the settings should rather be displayed or whether the inserter should continue to be displayed until the focus is changed to another area. One way or another: A central function would be to use drag-and-drop from the inserter, as mentioned here: #21080 (comment)
BTW: The plus icon would of course disappear from the top bar, which is not bad considering the lack of space described here: (#20877 (comment))
Disable the sidebar and still display the Floating Action button
The FAB should still be visible when the sidebar is deactivated. (Here the icon would also have to change, since there would no longer be only settings in the sidebar).
Display inserter temporarily if sidebar is closed
This would allow the inserter to be displayed temporarily - in an overlay that is slightly smaller than the sidebar, but still has a maximum height. Here the overlay should definitely disappear when clicking into the content area as well as after inserting the block.
Navigator Panel in the left sidebar without replacing Block Inserter
As a result, the left side could now be used for the Navigator.
This display of a table of contents is familiar to users from many applications (Apple Pages, Keynote, PowerPoint etc. etc.) and is, as already mentioned, discussed here: #22113
Drag and Drop blocks from Block Inserter into Navigator Panel
This finally leads to the fact that you can now use Block Inserter and Navigator Panel simultaneously to insert content there.
From my perspective, this would greatly enhance the Navigator Panel and save the "hitting the correct block" in the content area.
Alternatives:
I thought about inserting the FAB halfway into the sidepanel, as described here: https://material.io/components/buttons-floating-action-button#placement However, it turned out that then too often content in the panel would be covered up. Apart from that, this would certainly be interesting to create a closer proximity between sidebar and button.
The text was updated successfully, but these errors were encountered: