4 ms·
I don't think you listened to me, because you said this: > Now compare that to fighting default styles and complected component styles As I said, I am NOT fig
by gotaquestion 4y ago
I don't think you listened to me, because you said this:
> Now compare that to fighting default styles and complected component styles
As I said, I am NOT fighting default styles. I want them.
I don't WANT to write my own components, just change colors with Sass (and maybe some affordances).
I'm an engineer, not a UX designer, and I don't have budget to hire a UX designer (nor do I pretend to be good at UX like most programmers). Bootstrap is ideal for my situation, and many others in my position.
Also, what are you talking about? Tailwind absolutely does NOT give you out of the box components. Only third-parties, like DaisyUI and OP's link are fully formed components (or the links off of the tailwind page), which are at best like bootstrap and at worse an inconsistent mess.
- mimsee 4y ago> Also, what are you talking about? Tailwind absolutely does NOT give you out of the box components. Well, no. And that's by design. Should you want components, there's an official Tailwind UI[0] that the dgb23 also mentioned. Not to mention the uncountable amount of open-source component libraries. [0]: https://tailwindui.com/ https://tailwindui.com/
- dgb23 4y agoYes I get that, I wanted to illustrate the use case for tailwind (bespoke design) and why it makes sense there and how component libs can still be useful if delivered in raw form. I didn’t want to imply that your use case isn’t valid.