Sort order for categories.

[BE-Webdesign]

This is tied in with the inserter menu. What do we want the default sort order to be for the categories and blocks in those categories? This mainly becomes a concern when other plugins will be able to register blocks and categories.

[BE-Webdesign]

Also important to this topic is whether we want categories to be a one to one relationship or a one to many relationship for blocks.

[aduth]

one to one relationship or a one to many relationship for blocks.

What's the use case for one-to-one ?

[BE-Webdesign]

one to one is what we have right now for blockType => category and it is one to many for category => blockType, which on the whole is a one to many relation. (I think of relationships weirdly and do not have a CS degree, so I could be using the wrong terminology.) If we keep a blockType to only belonging to one category it will keep the ordering simple and displaying the blockTypes simple in the inserter, or wherever else we need to display blockTypes. But there could be a reason to assign multiple categories as an array i.e. Common and Media for image, video etc. If we go one to many we would want to do something like:

registerBlock( {
  namespace: core,
  name: embed,
  categories: [ 'common', 'media' ]
} );

If we want blocks to belong to many categories it will make displaying them a lot more complex. Maybe there is a user experience benefit that outweighs keeping things simple. So in total the relation would become a many to many, which are usually ugly to deal with unless the benefits of it are superior. I personally don't find an urgent need to have multiple categories for each blockType, but this would probably be a good decision for @jasmussen to chime in on.

[mtias]

We don't want a block to belong to multiple categories, at least for now. There's a PR to allow creating new categories. It's likely we could assign a plugin-block that hasn't specified a category to be under a "Plugins" category. Same for themes.