preline VS Tailwind CSS

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.

Sidekiq is already configured along with assets, tailwindsCSS.

Finally, for our front end, we’re going to be pairing Next.js with the great combination of TailwindCSS and shadcn/ui so we can focus on building the functionality of the app and let them handle making it look awesome!

You can use any frontend framework you want — react-based tooling, however, has a natural advantage as it models everything as a function of state, which can map 1:1 with the concept in Burr. In the demo app we use react, react-query, and tailwind, but we’ll be skipping over this largely (it is not central to the purpose of the post).

Tailwind CSS: A utility-first CSS framework for rapidly building custom designs.

First, you need to make sure that you have a working Tailwind CSS project…

Tailwind CSS

With better CSS approaches like TailwindCSS and Vanilla Extract (which we're heavily using) it's much easier to maintain the UI and make sure it doesn't change unexpectedly. No more conflicting CSS classes, much less CSS specificity issues and much less CSS code in general.

This app was built with Svelte Kit, Tailwind CSS, and many other technologies. For a full rundown, please visit the GitHub repository

Unlike Tailwind, which has over 77,000 stars on GitHub, Mojo CSS has about 200 stars on GitHub. But the Mojo CSS documentation is fairly good and you can find most of the information you’ll need there.