Web Component Version of Web Awesome

[tamara-nexus]

Hello I am wondering if is feasible to expose a non-framework version of Web Awesome, in addition to the framework ones. I.e.:

• Web components with TS (the main output from Lit)
• React
• Angular
• Vue

Logic: we would like to see if we can use it in some of our Java applications that use some legacy libraries / in our other simple UIs that are pure HTML and JS.

Questions:

• Would that be more work?
• Would there be issues with events?
  Basically am I missing something that would make this a bad idea?

Thanks!
Best regards,
Tamara

[claviska]

This sounds like Web Awesome free. The base product is a collection of open source components you can use however you like. Web Awesome pro adds additional components (the more complex ones), theming, patterns, and other great stuff in addition to the components.

[tamara-nexus]

Yes, e.g. we would be willing to look at pro e.g. for advanced data tables etc... but how can we also e.g. have the pro components in e.g. Java applications that do not use any of the modern frameworks (i.e. having a framework-agnostic version)? This has been the need in two companies I have worked for. Still no idea how to solve that problem, unify UIs across all stacks with one UI library. But I see your point above. I hope there would be way for this at some point.

[claviska]

We aren't building Web Awesome for a specific web framework like React or Vue, if that's what you're asking. The components and nearly everything we're producing will be usable with or without frameworks. (If I'm understanding you correctly!)

[tamara-nexus]

Yes that is what I am wondering about <3

E.g. when I was trying to test with Storybook (Web Components version), I was not able to see how to install and use it in docs (e.g. screenshot attached). At the moment I have my Storybook set up with Vue (for a different reason). But ultimately I would like to provide code snippets and guidelines that are easy to follow for different product framework and stacks (i.e. kind of Storybooks in one).

P.S. We are using Storybook to build a design system and test layout parts (e.g. composite components some from scratch very specific to us and some hybrid e.g. 2 Shoelace components bundled together for reuse e.g. user avatar and menu) and leverage its awesome features and testing tools before things go into actual UIs etc... so our purpose is create our branded layouts (and use off-the-shelf components - Shoelace is the closest to what we need / has the right mindset of being framework-independent e.g. if one needs to move to new frameworks later or have a new product in another framework etc...).

On a side note, my colleagues and I are very inspired by your team and we really appreciate your engagement with us in our conversations. It is not everyday that one comes across this. We feel that you all put a lot of thought into and it and think long-term. Have a great day. We are checking out for the day here.