re: How to write better CSS in teams with ACSS — A dynamic Atomic CSS library VIEW POST

re: From the article: It’s hard to write all those same set of classes over and over. Yes, it is. ACSS says it’s a component based framework. If you ...

It doesn't, really. If you're making a separate web component for every single thing on your site, like <actionbutton>, resetbutton, <edgecasebutton>, etc, then that seems like a never-ending task.

If you're just templating components, it doesn't make any difference to my argument - you still have to find which component does what and update the templates rather than updating the stylesheet. You have to change all your components rather than apply a theme. You can't switch between themes without re-building and deploying your site, and this all just feels like a massive step backwards.

code of conduct - report abuse