Is it me, or does semantic have a bad case of "over choice"?

[Bradley-H]

I'm looking through alot of what semantic has to offer, and I'm left with the feeling of being overwhelmed by what there is. I would like to use semantic, the concept is perfect from a developer perspective I'm left just feeling with over choice, like from inputs alone there are like 15 different options just for something as simple as that.

Also, I'm in no way intending on bashing Semantic, I think it's a great framework.

[romaninsh]

on the upside, i don't need any custom CSS files and all client requirement and tweaks can be done through the variety of classes.

[YamiOdymel]

The first thing I'd like to point out is the Color. The colors with .blue, .pink, .red has no meaning and which is not Semantic at all.

Should've replaced them with the .warning, .positive, .negative, .primary so people won't make their website full of the #RainbowPride colors.

This can also forced people to create a meaningful website.

[romaninsh]

Interesting point, @YamiOdymel about limiting colours. I've worked with designers in the past who were creating a fixed set of colours - palette. They haven't had any particular names, just numbered. In semantic it's possible to adjust the standard colours, but not redefine them entirely. That's a slightly different topic though.

[ko2in]

@YamiOdymel, I think there is nothing to do with being semantic or not semantic regarding the way we uses those class names for colors.

Such CSS class names .warning, .positive, .negative aren't about color. I couldn't say warning is red color. I could only say warning should present with red color.

[Atulin]

I think to limit the colour palette, SUI first needs to move to some sane way of handling themes, so custom colours can be easily added