4 ms·

Very welcome. Sometimes the amount of classes needed in Tailwind is enormous. I paid for the TailwindUI pack too. But as nice as Tailwind is, the guys who buil

Very welcome. Sometimes the amount of classes needed in Tailwind is enormous. I paid for the TailwindUI pack too. But as nice as Tailwind is, the guys who built TailwindUI don't really get or understand a lot of real-world design patterns. A lot of stuff in there is needlessly complicated. Our team end up trimming down things to 50% of the markup that they use, while retaining full responsiveness. Overuse of flex for simple paradigms is a constant complaint of mine. Hope DaisyUI improves Tailwind in some way. Anyway... sorry to get sidetracked on a sidebar.. lol.

Mike_Andreuzza 5y ago
>>>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.
nickjj 5y ago
There's also https://tailkit.com/ 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-tailwind-components-and-giving-away-2-copies https://nickjanetakis.com/blog/reviewing-tailkit-300-tailwin...
tailspin2019 5y ago
> 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.
- eric4smith 5y ago
  We don’t regret paying for it at all. Just pointing out its problems.
NaN1352 5y ago
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.
maxcan 5y ago
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.

Mike_Andreuzza 5y ago

>>>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.

nickjj 5y ago

There's also https://tailkit.com/ 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-tailwind-components-and-giving-away-2-copies https://nickjanetakis.com/blog/reviewing-tailkit-300-tailwin...

tailspin2019 5y ago

> 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.

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

NaN1352 5y ago

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.

maxcan 5y ago

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.