Pro support for building 3'rd party components.

[grokwich]

I may be off, but it seems that the upcoming Pro emphasis is focusing on using Shoelace (WebAwesome) in the context of building an entire webapp.
That's may be the majority case, so that's a cool place to start.
But i think one of the biggest strengths of Web Components is it's ability to plop a component into any context/framework.
This makes WebAwesome a great candidate for building 3'rd party components.
You may already be planning this, but i would request that you consider (where it makes sense) building out Pro with this particular usecase in mind.
Some examples might be...

• Layouts and responsiveness are also very important to composite Components (as well as full pages).
• When/how should the Shadow/Light DOM be used for 3'rd party components (guidance, patterns, code support)?
• Maybe special guidance/support for Slot use?
• How should 3'rd party components be correctly themed?
• Is there any way to ease theme building of 3'rd party components to match the styling of a host app (this could be an amazing application of AI).
• Can the theme builder be used to support 3'rd party components? It would be very nice is the Theme Builder itself count be adapted for 3'rd party component theme building. Would also be great if the Theme Builder was itself a "component" that could be packaged with a 3'rd party component(s) product for downstream customer styling.

Thanks for building such great framework!-)