Provide the frontend a way to distinguish module and theme components from one another

📌 Refactor XB internals to not assume /xb-components returns only SDC-powered XB Components Active introduces some additional structure that will make this much clearer to land.

Ready! 😊

Trivial update for /openapi.yml, tagging.

📌 Refactor XB internals to not assume /xb-components returns only SDC-powered XB Components Active landed!

📌 Add support for Blocks as Components Active is in, rebased.

Discussed this with @longwave and @jessebaker. We believe the extension_type key is too narrow and doesn't account for other needs we have for these. Essentially what we need is information on what is the source of the "component". Potential sources are: Blocks, Theme Components, Module Components, Elements, and JavaScript components. Each of these sources then have categories within itself. Here's a visualization of that:

As per the diagram repurposing this issue to add source.

category will be added in 📌 Define built-in components and categorization for components Postponed which is postponed on the core issue ✨ ComponentPluginManager must implement CategorizingPluginManagerInterface Active

source implementation in MR!419.

RTBC as far as I'm concerned, with one exception: docs/components.md should be updated to capture #10, and … why not embed exactly that diagram in that document while we're at it? 😇

wim leers → closed merge request !373

Added the categories requirement and Mermaid version of #10 to components.md.

Needs approval from @traviscarden.

Looks good!

Oops. You asked me to go ahead and merge. Done. 🙂

Automatically closed - issue fixed for 2 weeks with no activity.