windblade VS unocss

Really appreciate the support! Please note that it is in alpha and not on NPM yet (though dropping any day now) but you can find temporary installation instructions here

Someone has opened a feature request to add this to my UnoCSS preset. I don't know if you are the same person but I thought that was working code that was posted in my issues. Could you please specify what does not work correctly in your implementation?

Not exactly a suggestion because Windblade is in alpha and there are things missing but I would massively appreciate your feedback. You can find temporary installation instructions here because it is not on NPM yet.

I am working on a Tailwind-like UnoCSS preset that handles light and dark schemes automatically

Made with: - Windblade (my own version of Tailwind) - Solid JS - Vite

I think it is unacceptable that Tailwind does not do it itself. I am actually working on an UnoCSS preset I call Windblade that is like tailwind but with automatic colors (and other less notable improvements)

I am also working on a Tailwind-like preset but with better colors system, logical properties and a simpler config

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.