-
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
Organizing reusable blocks with categories or similar #7608
Comments
If #9964 ends up with opening the ”ordinary” editor for reusable blocks perhaps one solution could be to add a taxonomy to them which could be used for sorting them in the block list. |
Reusable blocks might as well be a tab next to the pattern tab in the Block Inserter. |
I agree that we will eventually need to be able to organise Reusable Blocks somehow. It's not clear how this will work right now, though, while so much is up in the air regarding Block Patterns and the Inserter. (See #21080.) |
I added an issue a while ago in relation to adding a drop down to the Blocks inserter panel (the same principle can be added to Reusable blocks as well). #26028 |
Here is an update. Showing what it looks like today. In relation to adding categories etc. |
Just checking on this for opinions on whether the new Patterns interface in the Site Editor, and changes in the Block Inserter has resolved this issue - or if user-designated categorisation of patterns would be helpful? |
Yes, it will be! |
Closing this out as we have converted reusable blocks to synced patterns and categories are now possible/slated for 6.4: #53164 |
Creating shared blocks is awesome, but what happens when you start getting a fair amount of them?
Things start to become hard to use, they take up screen space, finding that one block you wanted becomes a burden.
Adding some way to categorize shared blocks will likely be necessary moving forward, especially if we wish to do more in line with adding sidebar control etc to the editor experience.
#7606 looks like it might be a good stepping stone in that direction.
One might argue that naming your blocks to find them easier is the right choice, and using the block search after this to find them. Although that would be nice in a perfect world, with limited space for block names you just can't rely on naming alone.
The example above is possibly a bit extreme, possibly not, we don't know how users will choose to name things.
The text was updated successfully, but these errors were encountered: