tail-kit VS unocss

5. Tail-Kit

My favorite thing about Tailwind is all the sites that offer copy-and-paste components, ready to use. Sure, you can pay for TailwindUI, but you can also just browse components from e.g.

* https://tailblocks.cc

* https://blocks.wickedtemplates.com

* https://tailwindcomponents.com/

* https://merakiui.com/

* https://www.tailwind-kit.com/

* https://www.tailwindtoolbox.com/

Most of the sites I put together this year used an amalgamation of components from those sites for basic structure, and then just get customized to the brand. I hate writing raw CSS and I would also hate writing raw Tailwind.

Over 250 free components and free templates. For use with plain HTML, React, Vue.js, and Angular web applications.

Kutty Mamba UI Lofi UI Kitwind Tail-kit Tailblocks Tailwind Toolbox Treact

Tailwind UI is not Tailwind CSS. It seems you are looking for templates instead of coding from scratch. Tailwind UI is that! It is a paid service by the developers, but there are other alternative template libraries: https://tailwindcomponents.com/ or https://www.tailwind-kit.com/ for example

Tailwind Kit

I wish tailwind would support attributify like https://github.com/unocss/unocss, which is much more readable for complex layouts:

  link

I feel the same about people praising Tailwind.

Tailwind (and similar, I tend to use https://unocss.dev/) is not good for your frontend architecture BUT they allow you to be so fast, that it negates the benefits.

For a job well done, I'd follow the principles of https://maintainablecss.com/

I think UnoCss is may be better than Tailwind already and has a good Vue integration https://unocss.dev/

The most popular tools that implement this approach are: Tailwind, WindiCSS, UnoCSS.

- UnoCSS: https://unocss.dev/

haha, fair point. Still, I'm on the fence about how utility components are namespaced in USWDS. Perhaps giving users the flexibility to define the namespace might work better? One thing that bugs me is the absence of class-sorting like we have in TailwindCSS. Plus, there are some gaps I've noticed in USWDS. The naming, especially when comparing "padding-x-2" and "p-x-2", can be really annoying when switching around, maybe that could also be an option for the developer or project. Similar to the ideas antfu has on uno.css https://unocss.dev/ ♥

UnoCSS is a popular option

UnoCSS — for styling with Tailwind-like atomic CSS;

Some exceptional libraries and frameworks only support VSCode, which you could argue is a bad thing, but it makes sense, VSCode is the most popular code editor after all. For example UnoCSS only has a VSCode extension, and it's my favourite way to write CSS. Astro has a LSP but I've found that the experience in VSCode is much better than in Neovim.