The eternal pendulum swinging between BEM and atomic css forever. The best is to start with atomic and then extract a few BEM use cases as duplication emerges. Then you've got the best of both worlds.
Roughly half of css is extremely specific to one place and not worth extracting. The remainder though is actually important to the design system and is worth deduplicating and formalizing into BEM / variants. The trouble is when you try to BEM everything and end up with thousands of classes that are only used once.
@programming.dev
Welcome to the web development community! This is a place to post, discuss, get help about, etc. anything related to web development
Web development is the process of creating websites or web applications
Not sure what to post in here? Want some web development related things to read?
Heres a couple blogs that have web development related content
Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient
go to feed...
@programming.dev
Welcome to the web development community! This is a place to post, discuss, get help about, etc. anything related to web development
Web development is the process of creating websites or web applications
Not sure what to post in here? Want some web development related things to read?
Heres a couple blogs that have web development related content
Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient
go to feed...
Forever watching people reinvent CSS classes for no reason. (I appreciate that this article actually does show doing it with classes, but it's still grating to me that these "frameworks" just keep reinventing
style="...")save