Hacker News Reader

There's also https://tailkit.com/, the markup is pretty reasonable. It was designed by someone who has been making themes for ~10 years.

I did a review of Tailkit in general here: https://nickjanetakis.com/blog/reviewing-tailkit-300-tailwin...

Exactly. I paid for TailwindUI too but have been disappointed by the execution in code. I love the visual design, but give me some abstractions and not 20 classes per element.

TUI design + DaisyUI's abstractions is the dream.

> the guys who built TailwindUI don't really get or understand a lot of real-world design patterns

It's all relative. It's clear they understand more than I do, and I'm not a terrible UI designer, so paying for TailwindUI has been a no-brainer in terms of the value delivered to my projects so far.

We don’t regret paying for it at all. Just pointing out its problems.

>>>Our team end up trimming down things to 50% of the markup that they use, while retaining full responsiveness.

I have to agree with this.

I would suggest the use of convention like SuitCss for your custom component classes so you can lint them thoroughly to ensure low specificity.

I would recommend to use a prefix on your custom classes, to "namespace" them. "btn" is far too generic. This can even be linted by eg. postcss-bem-linter.