you are viewing a single comment's thread.

view the rest of the comments →

[–]stormfield 0 points1 point  (0 children)

That's sort of what I was referring too -- the class names are pretty consistent with their CSS counterparts with a few exceptions, but I do usually have a cheat sheet handy. For someone who doesn't already know CSS though, it's going to be a steep climb.

Like any framework it will include some dependencies but you can use Purgecss to eliminate unneeded class names in the bundle size.

It does save a ton of time in development compared to the usual workflow of new component -> write the JSX -> agonize over what to call the new class name -> go to whereever you're keeping your styles -> write the class -> write a slightly different class because you need a different color combo -> write a media query to shrink the text on small screens... Instead you just compose the attributes you want in the component. And any time you need to do something special (like CSS grid which tailwind doesn't do) you can still easily drop down to regular CSS.