Be the first to like this
For years now, frontend developers have ranted and whined about Drupal's divitis, a disease that's been greatly eradicated in Drupal 8 with the introduction of smarter templates and the use of Twig.
But a secondary problem often crops up for Drupal frontenders -- all the CSS classes, and corresponding styles, that Drupal stuffs into every element that's left. For some themes, Drupal's default classes give a nice starting point. For others, they provide hours of delightful fun learning about style cascades and specificity issues. In other words, they can be awful.
Drupal themers can be an ornery bunch, and for awhile now they've been arguing about which approach is better, like historical browser war re-enactors set loose on the Drupal issue queues.
No longer. A consensus has emerged, beginning relatively recently in Drupal 8 development, that allows themers to choose between including Drupal's default classes, and using none at all. Its name is Classy. Come hear about this brave new world, with such base themes in it!