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
@michelle Great article, much food for thought. Anecdote to add to the pile: I'm helping lead a team that is actively un-Tailwinding a large React design system in favor of using vanilla CSS (with a sprinkling of Sass). Things like custom properties for design tokens, component-level tokens which inherit from them, standard stylesheets without @ apply everywhere, etc. We're still keeping TW in the pipeline for some utility classes here and there in page templates, but otherwise…buh-bye! 😁
@jaredwhite thanks for sharing your experience! It’s interesting to hear other people’s experience with this and to know that it’s not a unique problem. Definitely agree that being able to generate utility classes is handy, but I’m leaning away from using them everywhere