[Needs design] Library confusingly lists SDC-sourced and Block-sourced Components together

See, I knew I vaguely recalled seeing that somewhere! 😄 Had no idea how to find it. Thanks, @lauriii! 🙏

Ah that makes sense but I also think that all these component listings/groupings should be 100% controllable from the server side, we shouldn't have any hardcoded restrictions - we should be flexible in allowing developers to customise the XB UI from PHP wherever possible. This means that even if the library and top bar have groupings (like the Sections/Components split we have at the moment), the number/names of those groups should be sent from the server.

This means that even if the library and top bar have groupings (like the Sections/Components split we have at the moment), the number/names of those groups should be sent from the server.

Agree 💯, this is the same sort of thing I was trying to say in 📌 Implement saving block settings forms Active but I think you've said it better with

we should be flexible in allowing developers to customise the XB UI from PHP wherever possible

- 🙌

@effulgentsia asked me if I have thoughts on how to split up the server-side vs client-side responsibilities here and design the API between them.

I think this is where having an OpenAPI spec comes in handy. We can use that as the discussion point. I'll open an MR with some changes to demonstrate what @longwave is articulating in #4

Proposed a change to the API spec for the components controller that should power this.

If we agree with this approach we can move to implementation

Some nitpicks but the proposal looks good to me in principle.

I took a stab at writing a more descriptive title based on where the conversation went.

Also, I thought it might be helpful to be aware that the designs for code components ( 🌱 [Meta] Plan for code components Active ) introduce the term, group. See ✨ Component groups for code components Postponed . Those are what we previously named category in 📌 Define built-in components and categorization for components Postponed . We may want to resolve that mismatch first before we choose the property name here. I would vote for renaming groups to categories in the code components world.