I hope this leads to a 'standard' way of developing Bootstrap-based templates. Something comparable to the submission guidelines on WrapBootstrap but codifying

I hope this leads to a 'standard' way of developing Bootstrap-based templates. Something comparable to the submission guidelines on WrapBootstrap but codifying how a template's assets should be arranged, written, etc. Using Bootstrap as a base for new template designs was a major step forward for the template industry because customers aren't walking into a completely foreign codebase with each purchase. If that familiarity were extended further then it could lead to interoperability of component styles between templates developed by different designers, which is something customers have brought up numerous times over the years. It's never quite that simple but I think for example simple namespaces would be a step in the right direction ('.unify .nav-tabs' and '.vitality .nav-tabs').