DEV Community

Discussion on: Building a Tailwind CSS badge component

Collapse
organizedfellow profile image
Jaime Aleman

one of the disadvantages that I've found that it does not come with a base set of components that you can use right away.

That is NOT a disadvantage, that is the absolute core feature of a utility first framework like this. This is nothing like Bootstrap or Materialize or Bulma, where components are already created for you. With TailwindCSS, YOU choose every border, the thickness, the color, the border-radius, the height and width of every single element of your design.

This is absolute freedom!

Collapse
sharakpl profile image
Sharak

With TailwindCSS, YOU choose every border, the thickness, the color, the border-radius, the height and width of every single element of your design.

With Bootstrap it's the same! All you need is setup scss variables just as you like. At least you still need just 2 classes to create a button you like everywhere instead of dozens of classes in every single button which seems pointless and total waste of time.

Collapse
zolidev profile image
Zoltán Szőgyényi Author • Edited on

Hey Jaime,

You are absolutely right. However, the fact that you get components right off the bat does not hinder your ability to use Tailwind as it was designed to use: utility first.

It is up to you whether you want to use a component such as a button or an alert and because these components are made out of the utility classes, and not OOCSS classes such as btn-primary will still let you work with Tailwind the same way you did up until now as well.

The style file where the Tailwind directives are imported for Flowbite has only three extra classes: for pseudo elements that could not be targeted with the utility classes. And that's optional.

Flowbite is absolute freedom, but a faster freedom :)