It really boils down to the use of global project settings. It makes perfect sense to me what’s happening though because it’s the nature of CSS.
Once you rely on global settings in Blocs you must use custom classes to override individual elements. That’s how Blocs works and that is consistent with basic css. The global setting is meant to override everything, but you can override the override with another class if needed…
With Card Designer you have more control than assigning an overriding class will allow. This is control that many other brics don’t have (they also rely on making classes to override a lot of things.) The trade off is that you won’t be able to use global overrides and have this type of control that I’m providing.
Here are my options
- I can eliminate the html tags that provide SEO value (i.e h2, h4, p, a) to a card.
- I can limit all features to only applying classes for making changes, thus eliminating a lot of goodness from the bric.
Neither of these appeals to me, and the trade-off is acceptable. Besides, the number of classes needed to make a card like this would be dozens and none of that would happen in the time CD will do it.