Revise and optimize relationship between original BS LESS files and the new UW UI Toolkit files that override them

[VidalQuevedo]

Approach:

• [x] First, override as much styling as possible via variables.less first
• [x] Second, override component files (such as navbar.less) by:
  • [x] Creating a new file with the same name and adding it to the bootstrap-override/ directory
  • [x] Importing the overriding file right after the original in uw-ui-toolkit.less file
• [x] Third, use overriding file ONLY to:
  • [x] Override original styles of existing components that couldn't be overwritten via variables.less (e.g. adding drop shadows to .navbar-inverse)
  • [x] Add new equivalent components particular the UW UI Toolkit (e.g. .navbar-uw-beige)
• [x] Ultimately, for examples/, add custom styles in separate .css files, just as BS does.

[jnweaver]

This sounds good to me. In point #4, do you mean we should keep those styles in a separate less/css file (separate from the main toolkit css)?

[VidalQuevedo]

Yeah, we'll keep them separate =)