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
{{ message }}
This repository has been archived by the owner on Mar 21, 2023. It is now read-only.
Right now, the way blocks are listed in the inserter is very open — its the Wild West. For example, if I install CoBlocks I get two new sections in the inserter's list of blocks:
If I also install the Jetpack, Atomic Blocks, and Ultimate Addons Blocks plugins, I get more groups — some with icons and some without. I've also noticed that some plugins will try to use color to "brand" their blocks:
Having a way to brand Blocks is likely going to be more important as we introduce the block directory. Having some guidelines and restrictions here would likely be of help to many developers — and lead to a more consistent UX.
--
Over in the Gutenberg area, there's been some discussion around regrouping the default set of blocks into a more user-friendly list. But I think as we integrate the block directory we'll (hopefully) see more blocks, and more people installing singular, individual blocks — as opposed to installing a collection of blocks, like Kioken or CoBlocks.
This presents an interesting problem. If you install a single block from CoBlocks, will you then get an entire section in the inserter with a single block listed?
This could lead to people having any number of sections in the block inserter with only a single block. Its not hard to imagine a scenario where you'd end up with 15 sections in the block inserter, most containing only a single block. This becomes unwieldy.
Now seems like a great time to reconsider the way blocks are listed within the inserter, and perhaps outline some guidelines to how developers are expected to place their blocks. It might also be worth standardizing the placement and color of icons, and forcing the placement of singular blocks within standard groupings.
The text was updated successfully, but these errors were encountered:
I believe blocks allow a "category" to be defined. For example, my P5.js single block plugin has category: 'formatting', defined in the block.js file.
Single block plugins should be taking advantage of this to insert their block in a pre-existing category if appropriate. Of course making their own category could seem like bonus advertising, but I'm not sure how to stop that from happening.
@mapk I’m suggesting we help avoid this by offering written guidelines and consider restricting the freedom developers have when it comes to creating groups and sorting blocks.
Right now, the way blocks are listed in the inserter is very open — its the Wild West. For example, if I install CoBlocks I get two new sections in the inserter's list of blocks:
If I also install the Jetpack, Atomic Blocks, and Ultimate Addons Blocks plugins, I get more groups — some with icons and some without. I've also noticed that some plugins will try to use color to "brand" their blocks:
Having a way to brand Blocks is likely going to be more important as we introduce the block directory. Having some guidelines and restrictions here would likely be of help to many developers — and lead to a more consistent UX.
--
Over in the Gutenberg area, there's been some discussion around regrouping the default set of blocks into a more user-friendly list. But I think as we integrate the block directory we'll (hopefully) see more blocks, and more people installing singular, individual blocks — as opposed to installing a collection of blocks, like Kioken or CoBlocks.
This presents an interesting problem. If you install a single block from CoBlocks, will you then get an entire section in the inserter with a single block listed?
This could lead to people having any number of sections in the block inserter with only a single block. Its not hard to imagine a scenario where you'd end up with 15 sections in the block inserter, most containing only a single block. This becomes unwieldy.
Now seems like a great time to reconsider the way blocks are listed within the inserter, and perhaps outline some guidelines to how developers are expected to place their blocks. It might also be worth standardizing the placement and color of icons, and forcing the placement of singular blocks within standard groupings.
The text was updated successfully, but these errors were encountered: