Michelle BarkerJan 17, 2023
Some thoughts about what if you don’t want to use a framework anymore: https://css-irl.info/disentangling-frameworks/

CW: Tailwind CSS. Anyone who mansplains Tailwind to me will be immediately blocked, no joke
CSS { In Real Life } | Disentangling Frameworks

A blog about CSS, front-end development, the web, and beyond.

CSS { In Real Life } | Disentangling Frameworks
Show threadRobbJan 17, 2023
@michelle I had the struggle of trying to de-tailwind something recently, so I couldn't agree more with this article
Show threadMichelle BarkerJan 17, 2023
@Robb Ooh interested to hear your reasons for de-tailwinding (if you feel like sharing?). I feel like the past year of CSS has made me re-consider using TW at all. Not sure I would bother if I was starting a new project now, despite a few advantages.
Show threadRobbJan 17, 2023
@michelle A client inherited a TW-based microsite built by a third-party, and nobody in-house had ever used TW before. They didn't intend on adopting TW elsewhere, so didn't want to spend resources on learning TW. At the same time, they didn't want to rely on contractors for every update either so they decided it'd be simpler to do a one-shot rewrite in the style of their other projects
Show threadMichelle Barker
@Robb Makes sense! We adopted it at the agency I worked at previously in part to try and increase consistency with the way CSS was written across projects. It definitely had some value there, but not so much on the projects I work on now
Jan 17, 2023 at 3:57pmWeb