Right yeah, I’m just not understanding the point of bootstrap style utility classes if the underlying framework is tailwind. The point behind tailwind and why I find it compelling is to not hide functionality behind a “btn-large” class for example. I’d much rather have code duplication but be able to see exactly how the css will behave by looking at the tailwind classes directly in the html. Going back to bootstrap style classes kind of defeats the purpose for me
Additionally flowbite does not code components in the way you’re describing. It’s just a site that provides tailwind specific example code using the tailwind classes directly
Sure, whenever I keep repeating the same block I just extract it to a Vue component. At that point I don’t need another framework, the component itself works fine and can be reused
Right yeah, I’m just not understanding the point of bootstrap style utility classes if the underlying framework is tailwind. The point behind tailwind and why I find it compelling is to not hide functionality behind a “btn-large” class for example. I’d much rather have code duplication but be able to see exactly how the css will behave by looking at the tailwind classes directly in the html. Going back to bootstrap style classes kind of defeats the purpose for me
Additionally flowbite does not code components in the way you’re describing. It’s just a site that provides tailwind specific example code using the tailwind classes directly
Not sure I get it, you aren't going to duplicate "px-4 py-3" 100 times or you might forget then have to guess. You will create a component.
But what's the point when you can just define it once and not need that extra component.
Sure, whenever I keep repeating the same block I just extract it to a Vue component. At that point I don’t need another framework, the component itself works fine and can be reused
No need for another framework on top of that
We need a word for backend frameworks that render HTML.
If you're using Vue then sure.