Migrate away from using Bootstrap selectors in markup

[bruth]

This is motivated by this post: https://coderwall.com/p/wixovg which describes using Sass @extend to "mix-in" Bootstrap styles, but using your own semantics. I don't think this is necessarily the way to go either, but it got me thinking regarding a strategy for #96. According to Chrome, 97% of the CSS is not being used. However more of the concern is around making it more clear how to extend and/or theme Cilantro components. Bootstrap is certainly familiar, but for defining a theme with familiar terms relative to the components, it is hard to describe in terms of Bootstrap classes.

That all being said, a theme definition needs to be written up to understand the scope of the Cilantro UI and what all is required. As with any custom interface, components are refined in which the original styles/layout (default Bootstrap) is no longer used. For the boilerplate components, there are plenty of small libraries such as:

• http://bourbon.io - cross-browser CSS mixins (which we already use)
• http://neat.bourbon.io - mixin-based grid system; this allows defining which components use a grid and can tailor components with custom sizes
• http://bitters.bourbon.io - lightweight scaffold styles, but is driven by Sass variables for high customization

[bruth]

Interesting project to remove unused CSS https://www.npmjs.org/package/grunt-uncss