Not buying the @tailwindcss kool-aid I’m afraid.
> I’ve written a few thousand words on why traditional “semantic class names” are the reason CSS is hard to maintain
So don’t use semantic class names! Use custom elements. app-card. image-viewer. Use HTML attributes for behavior
> I’ve written a few thousand words on why traditional “semantic class names” are the reason CSS is hard to maintain
So don’t use semantic class names! Use custom elements. app-card. image-viewer. Use HTML attributes for behavior
<custom-modal size=“large” open>…</custom-modal>
then simply write:
custom-modal[size=“large”] { … }
Use CSS variables as design tokens for site-wide theming. Shadow DOM yes/no? Up to you!
Tailwind is a really interesting idea…for the era prior to the one we’re in now!
then simply write:
custom-modal[size=“large”] { … }
Use CSS variables as design tokens for site-wide theming. Shadow DOM yes/no? Up to you!
Tailwind is a really interesting idea…for the era prior to the one we’re in now!
Can you count how many <div> tags are in this basic example? 14 I think?
This isn’t how you HTML, people! Write markup that *actually describes in plain language what the structure of your document is*.
This isn’t how you HTML, people! Write markup that *actually describes in plain language what the structure of your document is*.
Sorry, I know there are a LOT of Tailwind fans out there and you’ll probably unfollow me now. That’s fine. I don’t have too many programming hills to die on, but taking full advantage of the glory that is HTML5 is one of them. Tailwind is…the opposite of that! 😭
OK OK, I’ll stop now 😜
• • •
Missing some Tweet in this thread? You can try to
force a refresh
