It's funny how the solution (use CSS as it was intended) is now being transformed into JS-powered component solutions.

But yeah take say a dashboard layout with a lot of cards of different sizes. They're going to have the same underlying design, padding, rounded edges, background colors, etc -- and usually only vary on maybe size and breakpoints.

This is all very well solved in semantic web, but it feels to me like the JS + Tailwind apporach is creating new problems and thus new solutions to accompany.

I think the detail is that this JS answer is really only for people working at a seriously large scale. At that size, there is absolutely zero room for non-componentized logic as cross-managing a billion pages with duplicate HTML elements is pretty unacceptable. That said, Tailwind also allows you to define your own classes that apply multiple TW classes.

> This is all very well solved in semantic web

If it was solved with "semantic web" (whatever that means), we wouldn't have people attempting to solve this again, and again, and again.

That's patently false. The webdev community does nothing but reinvent/rediscover the wheel e.g. SSR.

What does SSR have to do with semantic web?

All "semantic web" can provide is a flat CSS namespace and a bunch of nested divs.

Even if you do everything right there's nothing semantic about it: https://inclusive-components.design/cards/

> If it was solved, people wouldn't try to solve it again.

Remember when serverless got invented even though CGI already existed?

I'd say it was rebranded :)