Sounds like using a subset of tailwind classes, focusing on positioning. This is what I’m doing on a nuxt project. I also use Sass for the visuals within each c

Sounds like using a subset of tailwind classes, focusing on positioning. This is what I’m doing on a nuxt project. I also use Sass for the visuals within each component. That said I never found utility classes enough to handle breakpoints, it’s hard to read and understand when using only classes in the html. There is no space anywhere to document what the breakpoints achieve. As usual, using multiple approaches is the best way to solve a problem rather than stubbornly sticking to some ideal like doing everything in tailwind, or using BEM naming religiously. Also BEM syntax sucks. It’s really long and unsightly. SuitCSS is much nicer, plus it has a linter.