tailwindcss-forms VS unocss

The forms plugin is similar to the typography plugin. Because Tailwind CSS’ resets also affect form elements, the job of the forms plugin is to give form elements a set of pretty, default styles. The default styles are minimal so you won't want to use them as is, but they make a convenient base you can override and extend.

Let's copy a form component from HyperUI, and edit it to make it work for us. If you use one of their form components, make sure to install the TailwindCSS forms plugin.

Install tailwind css and tailwindcss/forms.

If you're in a hurry: https://github.com/tailwindlabs/tailwindcss-forms

Finally Tailwind is the last CSS framework it can generate, which also has checkbox labels to the right: https://tailwindcss-forms.vercel.app/

We'll also utilize Tailwind's Forms Plugin to make it easier to style our Auth component, so let's install that as well:

I want to install tailwindcss-forms plugin on Deno but couldn't.

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.