ddahan/ui-libs

A UI Lib Picker for Vue 3 / Nuxt 3

ui-libs's Issues

Review/Add more libraries

Hi, there! The following libraries can also be added to the data 🙌

• https://github.com/chakra-ui/zag -- https://zagjs.com/
• https://github.com/chakra-ui/ark -- https://ark-ui.com/
• https://github.com/chakra-ui/chakra-ui-vue-next -- https://next.vue.chakra-ui.com/

---

• https://github.com/radix-vue/radix-vue -- https://radix-vue.com/
• https://github.com/oku-ui/primitives -- https://oku-ui.com/primitives
• https://github.com/agnosticui/agnosticui -- https://www.agnosticui.com/

---

• https://github.com/jd-solanki/anu -- https://anu-vue.netlify.app/
• https://github.com/uiv-lib/uiv -- https://uiv.wxsm.space/
• https://github.com/onu-ui/onu-ui -- https://onu.zyob.top/

---

Add new filters

These are other filters I have in mind, and could be added in the future.
Feel free to give feedback about the relevance or propose other filters that would be very useful to you.

• primitives (the goal would be to make a better distinction between UI Components libs rather than Primitives libs like headless UI, radix-vue, etc.)
• activity level (a way to measure activity on the repository)
• tree shakable
• i18n support
• Grouping support (e.g. libraries which support button groups - because it's painful to consider this like components themselves)

Newer Library : Tailwind-Elements

I have not tried this out yet, but I figured passing it along was still valid. I can review it after we check it out, but we are neck-deep in a project, and a peer developer mentioned it to me.

https://tw-elements.com/

Add an easy way to see dependencies

Some libraries rely more on dependencies that over.
It may be useful to some users to see at a glance the dependencies list.

Add links to demonstrate the information

Currently, for both features and component availability, you can just see a boolean value.

It could be useful for users and for maintainers too to have links pointing to the information:

• For a component, it would be the page of the component
• For a feature, it would be a page of the documentation showing the information

Notes:

• The information could be added in a popover.
• This should stay optional, as sometimes the information is not in the documentation.

Commercial Plus Vesions

Some of the offerings have a free version and then a commercial version on top. In those cases the selector would be better service if those were shown individually. This is especially important if the target use is for an open source library, and they need to know up front limitations in the free version because those features are only provided in the paid version.

It uses templates to build a react UI library Picker

Hello, I would like to ask if I can use your project as a template to build a react ui library picker

Add Storefront UI to the list

Hey there!

Really nice list of UI libs to use in your next Vue project.

I would like to recommend to add https://vuestorefront.io/storefront-ui to the list.

I can create a PR if you agree this library to the list :)

Review the "free" filter and add blocks

Based on #16, it appears that:

• Free filter is currently not very useful (as it removes tailwind UI)
• Some companies prefer paying products to ensure proper support
• Some companies are interesting with blocks too, and that it could be useful to know when they are available
• If there is something to pay, it could be great to know what exactly (additional components, blocks, etc.).

Add arco-design/vue

Link: https://arco.design/vue/en-US/docs/start

Add a per-component View

Currently, we can see for each library, what are the available components.
I'm wondering if the reverse view could be useful: picking a component, then seing all libraries that have it.
If it is actually relevant, I'm not sure how it should be designed.
Feel free to give feedback.

Add component thumbnails in addition to description

Currently, components are described with a title and a description.
It would be great to have some thumbnails to be more explicit about the utility, like the Daisy UI screenshot below.

However:

• Using existing ones like daisy UI don't solve the case where the component is actually not in Daisy UI.
• I'm not sure I would be allowed to reuse this images.

This implies that work should be done from scratch, and could be very time consuming.