Suggestion: Using StencilJS for Unified Components

Hello Flowbite team,

Firstly, I'd like to thank you for this fantastic project. I've been using Flowbite in my applications and genuinely appreciate the effort you've put into it.

Context:

While integrating Flowbite into my projects, I noticed that the library has distinct components for React, Vue, etc., and each is its own separate project. This led to me having to blend direct Flowbite components with components I created from primary styles.

Suggestion:

I was wondering if you've considered using a tool like StencilJS. StencilJS allows you to create native web components which can then be embraced across various frameworks like React, Vue, etc. If Flowbite could have a native web component base, it might ease integration across different frameworks and potentially simplify the structure of your repositories.

Benefits:

A unified set of components across all frameworks.
Reduced duplicated code and maintenance across separate projects.
Users can adopt components in any framework seamlessly.

Conclusion:

Understanding that the individual framework libraries are community-maintained, unifying the efforts could be beneficial for the overall quality and breadth of components offered. From my perspective, the visual aspect of Flowbite stands out as its strength, whereas integration with individual frameworks seems to be a weaker point. By adopting a unified component approach, such as with StencilJS or similar, the community could centralize their efforts, which could lead to a more robust, high-quality library that's easier to integrate across various frameworks. I believe this would enhance Flowbite's appeal to a broader audience and potentially reduce duplicated efforts.

Thank you for your time and consideration!

No files, tests, or entry points are identified in the issue. Begin by evaluating the proposal to use StencilJS or similar native web components across the separate framework projects, and define whether a unified component base is feasible; done would require an agreed implementation scope rather than a single isolated change.