I agree, exposing the defaults may help make clearer what the user is overriding when editing.
This is definitely an interesting conversation - @Marius, for the sake of clarity, what distinction are you making between blocks and elements in this case?
Given that element styles created in the Global Styles > Elements > Blocks affect the blocks we use and that according to what @yankiara mentioned above, that Section and Container elements created in Global styles without a class specified are used to affect the default styles for those blocks, there is an intrinsic link between them that is worth clarifying.
This is a point for itself which is worth reconsidering the current implementation.
We don’t need dedicated defaults with special functionality or UI (which could then confuse users, as @Louis is worried about).
It would be completely sufficient to ship Cwicly with regular and prefilled global element items which holds the current defaults.
If one doesn’t check on front-end which styles are applied by default, no one knows. This information not only should, but it needs to be accessible inside the builder itself.
It’s not even a thing of providing additional info for non-advanced users who build visually only (without dev tools, etc.), it’s a lack of info in general.
The default styles must be present in the editor in some way, so why not taking this opportunity?
