preline VS unocss

Today, I've released the Gowebly CLI v2.4.0 which includes Preline UI components library support for the frontend.

You can also check out

https://preline.co/

Which is basically what Tailwind UI should be.

Works with anything.

Preline UI provides a rich collection of 300+ prebuilt Tailwind CSS components. It has also 160+ starter pages and examples you can use to speed up the development process. It offers the largest Figma-free design system with lots of bells and whistles inside.

If you want to get a preview of Flowbite try Proline it’s very similar but free. https://preline.co

Thanks, http://preline.co/ is awesome 👏

Hey, I use tailwind, and then find some inspiration, you can find great component libraries that save you so much time, eg: https://www.hyperui.dev/ , https://mambaui.com/ , https://flowbite.com , https://preline.co/

And Preline

Preline is a fork of Flowbite for which they refuse to give license credits for — the authors of the package were originally left there (they forgot to change the package.json file) and the evidence is in this commit on their repository.

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.