This is cool. I can see how valuable this would be for slightly complex html elements. I'm not sure we should avoid using a css class like 'panel' though when it's worth it.

Say I want my tag to be styled like my panel divs. Their similarities are semantically only visual. A css class offers more flexibility in this instance.

But then you've got this situation where some utility classes are @applied like the old days and some are "free-floating" in the html. Styling info ends up in two places which doesn't sound great.

I'm starting to wonder if perhaps it could be of benefit to think about layout information and styling information as two very different things. If I put a top margin on an element that is specific to the element I'm working on. But if I make a button a certain colour and font that's a design rule that should have repercussions through the whole page.

CSS is hard.

Reduce CSS Class Repetition with Blade Components

This Series Has Been Archived