Why Tailwind CSS Won

Re:Why Tailwind CSS Won by LtdJorge on Wednesday August 16, 2023 @06:22AM (#37144998)

I assume OP means that for the fist button of the site, as in creating the site from 0.

[ Parent | on HN ]

Re:Why Tailwind CSS Won by xigoi on Wednesday August 16, 2023 @06:28AM (#37145040)

In that case, you just write

    button {
      /* your styles here */
    }

to set a precedent for all your future buttons.

[ Parent | on HN ]

Re:Why Tailwind CSS Won by troupo on Wednesday August 16, 2023 @07:11AM (#37145314)

In that case you end up with fifteen different variations of that button, class names like "button-cta__hero__overlay" and a smattering of !importants to defeat the cascade you can't chase down

[ Parent | on HN ]

Re:Why Tailwind CSS Won by xigoi on Wednesday August 16, 2023 @07:18AM (#37145365)

I've never ended up with something like this.

[ Parent | on HN ]

Re:Why Tailwind CSS Won by withinboredom on Wednesday August 16, 2023 @07:38AM (#37145537)

Work in bigger teams with bespoke css. It will happen ... eventually ... without fail.

[ Parent | on HN ]