[dwmbt]

i mentioned this in another comment but one takeaway i got from using tailwind is that it changed the way i look at css. i use it as a learning tool as well, which is something i rarely ever get out of solutions that try to do most of the heavy lifting in a project.

consider this comment an open-invitation for other good css references!

[paulgb]

> consider this comment an open-invitation for other good css references!

I'll take you up on that! Any good resources for learning tailwind that jibe particularly well with your “learning tool” approach?

[01brett]

Author here, I would also highly recommend Josh Comeau's CSS for JS Devs course. He covers fundamentals useful in all styling approaches.

https://css-for-js.dev/

[dwmbt]

i've heard a lot of great things about this course. like, a lot. i'm pretty broke so most of my money goes towards tuition and rent, maybe i'll ask for this for christmas!

[dwmbt]

i would say the tailwind docs themselves and looking at the examples were a big help. for instance, the way they visualize their flex elements was enlightening. also, learning about how atomic css is a useful paradigm was the biggest motivator for writing more meaningful and expressive css. i'll list some things i've bookmarked:

[0] https://css-tricks.com/lets-define-exactly-atomic-css/ [1] https://adamwathan.me/css-utility-classes-and-separation-of-... [2] https://acss.io/thinking-in-atomic.html

and finally, it's always useful to read critiques. the following article is well written, in my opinion: https://www.browserlondon.com/blog/2019/06/10/functional-css.... through that i learned that tailwind has a useful feature: @apply, which you can use in conjunction with a standard css class approach. i.e container { @apply color-grey-100; box-sizing: border-box; }