I don't think this is a very good example of divitus - or a good example of too many classes? / and also - bad advice to use ids here.
Almost any site you find will have 5-deep nested divs for no reason when there have been proper semantic elements since 2010. Many times now, it's because React requires a root element for boring reasons.
I don't see any reason to use an ID for anything but an anchor link. And definitely, no reason to style with them.
Just saying!
If you want an example of divitus and classitus - then just check out Tailwind CSS. That seems to be its main thing:
I don't think this is a very good example of divitus - or a good example of too many classes? / and also - bad advice to use ids here.
Almost any site you find will have 5-deep nested divs for no reason when there have been proper semantic elements since 2010. Many times now, it's because React requires a root element for boring reasons.
I don't see any reason to use an ID for anything but an anchor link. And definitely, no reason to style with them.
Just saying!
If you want an example of divitus and classitus - then just check out Tailwind CSS. That seems to be its main thing:
that markup is not semantic, those elements should semantic css class names too, not just littering of "utility-first" class names
unreadable