My usecase is that the design of the templates is being done
independently, at the time being. So I'd like to avoid any possible
conflict.Anyway, I would expect that any additional class used
internally by the software, not customizable, use a namespace to avoid
conflicts with an already existing css (especially with a common name
such as "section"). It's awful that it uses "section" instead of
"cq-section" or "aem-section".