Tailwind CSS
Hello guys I just started using
Tailwind CSS and I find it very interesting to use but I've got a question to ask.
⬇️
How else can Tailwind CSS be used without writing it inline html tags? Like is there another way to use it rather that just writing them in the tags, my code really looks ugly after writing lots of it in tags and I'm just curious.
What if I've got a big project to work on ? Is that the only way to actually use tailwind?10 Replies
welcome to tailwind
it's the only way to use tailwind that makes sense. If you're combining classes using SCSS or whatever else, to then apply them to elements using regular CSS selectors the "added value" of tailwind is just lost
I say "added value" in quotes because I personally don't think it adds that much value 🙂
composing everything in the class attribute and having a ton of utility classes is just what tailwind does, and if you hate it, just write your own CSS. I know most people on this server do just that
To be honest, the general opinion of the most active users over here is a bit against tailwind. Don't let you discourage by it. If you like to use it, and in a practical way, do
Btw, you dont have to use only tailwind. you can still make your own classes in regular css
This is really helpful thanks
Thanks
you might get some other answers if you ask on LBT as well, I know they're much more pro-Tailwind over there
ohw, and if you have questions, you can still ask them over here as well, we won't bully you away 😉
Lol you two, tailwind is just CSS though. We love CSS here. 😶
I’m a really big fan of it because with the vscode extension and a well written tailwind config, you can get some amazing color, font, spacing, media query, hover, and focus-visible style writing speed.
Using it outside of the HTML requires a bit of webpack know-how and a bit of boilerplate. Set it up with scss and postcss processing and you’ll get nice mini fixed production bundles and just an insanely quick way to move through style sheets. It’s not for everyone but if it’s set up well it just makes sense.
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
I mostly don't see the point to tailwind if you're using scoped css in a component framework, which if you aren't, what are you even doing at this point?
I've got maybe three to five selectors in an average sized component, and they're usually just straight up on either a single class, or more often just on the element name