Post B6KhRwPOBGNjMib2gq by b0rk@jvns.ca
 (DIR) More posts by b0rk@jvns.ca
 (DIR) Post #B6KhRud8nAC3qn0zqa by b0rk@jvns.ca
       1 likes, 0 repeats
       
       moving away from tailwind, and learning to structure my CSS https://jvns.ca/blog/2026/05/15/moving-away-from-tailwind--and-learning-to-structure-my-css-/
       
 (DIR) Post #B6KhRvTFfPsSSPOc4W by b0rk@jvns.ca
       0 likes, 0 repeats
       
       one thing that surprised me when moving away from Tailwind is that actually there were a lot of practices from Tailwind that I wanted to take with me into my new CSS codebase, and it helped me see how much I actually learned from using Tailwind about structuring CSS(2/?)
       
 (DIR) Post #B6KhRvwfu1PfvfA6vw by b0rk@jvns.ca
       0 likes, 0 repeats
       
       something I always find frustrating about tailwind is that it often starts flamewars (tailwind is the best! tailwind is ruining everything!) and so I wanted to write about how I think it isn't right for me anymore but I'm grateful it was there for me and I learned something from using it(3/?)
       
 (DIR) Post #B6KhRwPOBGNjMib2gq by b0rk@jvns.ca
       0 likes, 0 repeats
       
       also I haven't managed to formulate my thoughts about this in the blog post yet, but part of why I wanted to move away from Tailwind was this post really stuck with me https://thoughtbot.com/blog/tailwind-and-the-femininity-of-css I think CSS is an incredible technology and that CSS experts are amazing. People devalue CSS all the time and it sucks. I see that happen all the time here in my replies to my CSS posts on Mastodon. I don't want to use something that contributes to the devaluing of CSS as a skill.(4/?)