4 ms·

While I am sure that people will be using this, this product simply and completely disregards what Tailwind was designed for: Rapid development by building from

While I am sure that people will be using this, this product simply and completely disregards what Tailwind was designed for: Rapid development by building from utilities in just HTML and extracting into CSS components later. To quote from the Tailwind website: "Instead of opinionated predesigned components, Tailwind provides low-level utility classes that let you build completely custom designs without ever leaving your HTML." You can agree or disagree with the paradigm -- but if you disagree, there really is no point in using Tailwind :)

kemyd 7y ago
I can't agree. Tailwind is against components like "card" in Bootstrap. We do not use any custom CSS to build our components, only classes from Tailwind CSS. :)
milsebg 7y ago
I really don't think this is a contradiction: First, Tailwind encourages you to use apply to build reusable components, second, Taking building blocks from a generator like the one posted here, makes at least to me more sense than it would be for Bootstrap: You see a component and can (thanks to utility classes) see how it's built and change the appearance relatively fast. With Bootstrap you would basically just add a component class and that's it - customizing is more complex then.
dimfeld 7y ago
It's notable that the creator of Tailwind, Adam Wathan, is working on something similar [1]. Whether it fits the paradigm or not, there definitely seems to be a demand for such a thing. On a recent episode of the Full Stack Radio podcast [2], Adam talked about his own upcoming Tailwind UI release and said that he hoped the utility class design of Tailwind would enable people to use the predesigned components as a starting point and easily customize them, should they desire. [1]: https://www.tailwindui.com/ https://www.tailwindui.com/ [2]: http://www.fullstackradio.com/123 http://www.fullstackradio.com/123

kemyd 7y ago

I can't agree. Tailwind is against components like "card" in Bootstrap. We do not use any custom CSS to build our components, only classes from Tailwind CSS. :)

milsebg 7y ago

I really don't think this is a contradiction: First, Tailwind encourages you to use apply to build reusable components, second, Taking building blocks from a generator like the one posted here, makes at least to me more sense than it would be for Bootstrap: You see a component and can (thanks to utility classes) see how it's built and change the appearance relatively fast. With Bootstrap you would basically just add a component class and that's it - customizing is more complex then.

dimfeld 7y ago

It's notable that the creator of Tailwind, Adam Wathan, is working on something similar [1]. Whether it fits the paradigm or not, there definitely seems to be a demand for such a thing. On a recent episode of the Full Stack Radio podcast [2], Adam talked about his own upcoming Tailwind UI release and said that he hoped the utility class design of Tailwind would enable people to use the predesigned components as a starting point and easily customize them, should they desire. [1]: https://www.tailwindui.com/ https://www.tailwindui.com/ [2]: http://www.fullstackradio.com/123 http://www.fullstackradio.com/123