8 comments

[ 4.9 ms ] story [ 23.5 ms ] thread
One of the big reasons I love Tailwind is because of the book Refactoring UI by the author of Tailwind.

I am primarily a backend end person and Refactoring UI really helped me when trying to make a nice front end. Tailwind is the encapsulation of those principles in a nice CSS library.

I thought you meant like an old school O'Reilly book. For anyone else who was curious I believe this is the link:

https://www.refactoringui.com

It looks really good.

It’s a really solid book for engineers who just want to focus on the backend but need a good enough front end.

Several of my less front end focused engineering friends just love it.

Those are nice but superficial? the big one is avoiding cascading.
Tailwind has been a huge influence in how I think about styling my html, the way all elements are reset to the same box behaviour, or the rich color pallet, the naming conventions and so on. However I have taken those learnings and have gone back to writing css in a single style file using more advanced techniques like nested classes and psuedo-private properties but mo more pre/post processors. It fits my way of working very well because I think about my css like a functional design language where you can compose basic elements into the desired behaviour. I am mainly interested in creating wapp apps vs web pages so your mileage may vary.