skeleton VS shadcn/ui

GitHub: 4.6k stars License: MIT

Hi everyone, I'm so happy I can finally share the project I've been working on for the past few months. Ato UI is a themeable component UI library built with UnoCSS (with the Tailwind + Windi preset) and offers both styled and headless components, since the library is build on top of other fantastic headless libraries like Headless UI and Grail UI. Skeleton was also a big inspiration, as you'll be able to see in the designer page and the token system.

Vue 3 (with is quite close to Svelte in terms of DX, but Svelte has the edge here. Svelte is so simple, elegant and concise.<p>The biggest advantage of Vue is the ecosystem. However, Svelte is catching up. Some interesting UI component libs have recently arisen, e.g. <a href="https://skeleton.dev" rel="nofollow noreferrer">https://skeleton.dev</a>.<p>Performance wise, both are super fast.<p>Make sure to check out Sveltekit, even for building pure SPAs. The routing and data loading are worth it alone.

Should I use a framework independent library like DaisyUi or something related to svelte like flowbite-svelte or skeleton? Do I need svelte components? Should I build them by myself with DaisyUi?

I am using https://skeleton.dev for a dashboard and it is pretty amazing!

Hi, I've created a project with the skeleton.dev scaffolding tool:

In case anyone finds this who is also interested: I just stumbled upon an implementation of shadcn/ui components with css modules that looks pretty solid: https://github.com/qwalker8408/shadcn-css/tree/main

Hopefully something like this will be made official - at least there is some discussion going on in the shadcn/ui repo: https://github.com/shadcn-ui/ui/discussions/2832

shadcn/ui

For this project, I used PureScript + React + Tailwind css + shadcn/ui components. I assume you’ve heard of the first two (if not, see PureScript overview). The other two are blessings for the copy-paste-driven development.

The frontend of Zentrox is written using React. Of course I did not write this frontend without any frameworks. I use Next.JS by Vercel as a framework. Zentrox also uses a UI library called shadcn. Shadcn is an amazing library. It made devloping frontend a lot easier when you do not have to build everything from the ground up. I'd also like to give some credit to Radix UI, as this is what Shadcn uses for its components. :-)

I used Tailwind CSS for the styling because it's fast and easy to use, after a second thought I decided to use shadcn/ui so I did not have to build the components from scratch.

We started migrating some of our internal tools to https://ui.shadcn.com/ . We did not want to reinvent the wheel because it would take too effort (and we did try a couple times and failed).

If you're familiar with shadcn/ui (and if you're not, you should check it out!), you'll get what I'm going for here. asterisk/ui also follows the same core idea of providing open source, beautifully designed components that you can copy and paste into your apps, only in this case, the components are animations instead of styled primitives. It's all about making your life easier and your projects prettier.

Today, let's take a deeper look at two of the top contenders: Radix UI and ShadCN. Both these libraries have something different to bring to the table, and by the end of this post, you'll have a clearer idea of which might best be suited for your next project.

Living in the web development world, it may just feel like digging for treasure until you find your tools. If you're just starting now, well, you're in luck because Shadcn is packed full of awesome components that can make life so much easier.

Shadcn/ui