Tailwind CSS! Ever wondered what it was? How is it different from Boostrap or what makes it better? Learn what utility classes are and how they can possibly make you never go Vanilla CSS again, learning resources provided! treciaks.hashnode.dev/tailin…

Tailwind CSS

Tailwind CSS resources and tutorial.

treciaks.hashnode.dev
10
28
3
144
What I get from this is that it is all about the selectors. Structuring your CSS is an important part of the work. If Tailwind fits that’s great. For a design engineer it’s one of many approaches that’s nice to have at your disposal.
1
2
Hi Egor long time! Can you explain to me a used case or two I'm getting so sick of Frameworks I swear I will throw myself off a building if another one comes out CSS or JavaScript or anything else it's just a personal pain at this point I'd be interested in your thoughts!
3
1
2
This requires a long answer, maybe even worth an article. The impressive thing about Tailwind is that it found away to use the utility class name approach for everything. However, no matter the project over the years I haven’t been able to use it. It’s use case is rather narrow.
2
1
The 'styling' problem isn't libraries like Bootstrap or Tailwind it has more to do with how they're implemented. Writing CSS in a structured way and abstracting it away from the markup is what class attributes are good at. Tailwind has done away with that decoupled approach.
1
2
Tailwind, and Bootstrap to a lesser degree, have integrated their API, utility class attributes, with the markup. If you don't own the markup then you end up writing a custom abstraction. Adding hard to manage complexity.
2
1
If you create stand-alone applications or websites and don't share or reuse code with other web stacks then using Tailwind in such cases accelerates development and reduces knowledge and skill pressure from the team.
3
1
I work on design systems with multiple code stacks (using React, Angular, etc.) spread across multiple platforms, including CMS-based template components. I have limited control over the markup, which makes using something like Tailwind very problematic.
1
1
Replying to @dutchcelt @TreciaKS
Thanks for the clarifications Egor. I've not transitioned well to frameworks, abstractions and componentization for actual web sites. I see them as a blunt force way of development, making markup nearly unnecessary as a declarative approach. And, more difficult with which to work

Oct 23, 2021 · 1:36 PM UTC

1
1
Replying to @mholzschlag @TreciaKS
The irony is that these frameworks do help with the heavy lifting and elevate some development pressure. However, from a product perspective, they only move the complexity elsewhere.
1
1
Exactly. That's software, apps. Not really a web site. I am beginning to think our media="all" idea has yet to be done and that we were wrong that an actual content rich site would port well to apps. I am definitely grumpy about framework overkill. 😔
1
1
more replies