Gh pages audit

This audit covers the overview and usage section for each component. The examples sections will come next (there are plans for gist driven examples with jsfiddle type tinker-boxes). Lots of work to be done yet here, but, I think this is a good stopping point for the "first pass".
Yes, the primary audience is developers at ExactTarget (being open source is secondary).  And a majority of the work an ET developer will do is on existing applications.  Most of their time spent with Fuel UX will be with upgrading to a newer version, fixing existing bugs, and adding more functionality.  They will occasionally make a new application from scratch, but that will be rare.

The result of this is that we should _not_ optimize for FTUX, rather for the "pro user" who will repeatedly access & scan these docs looking for a specific "gotcha" until they're familiar with all of Fuel UX (which will take awhile).  Also, we want to make the UX for an ET developer as nice as possible.  Fuel UX's adoption will only be as good as _other people_ are willing to use it, forcing its use will not help and will also piss people off.