Rely on `site.url` which is different for production. In that case do nothing with the search result, otherwise when in development remove our url from it.
* Restyle code element, clean up variables
- Removes the padding and background-color
- Changes the color to a brand color ()
- Add new variables to kbd element styles to account for removing the code ones
- Remove overrides that were needed previously
* only break between words, and override it in the pre
* make file inputs 100% wide
* scope custom file changes in input group for sizing
* shorter button labels for responsive
* narrower cards
* button was too wide
* downsize
* fewer links in pagination
* redo cell text
* improve overflow docs
* Fix docs horizontal scrollbar in Components > Modal
* Add overflow to docs example class
* Drop the handleUpdate() variant
While I understand the variant covers the "get a particular plugin instance" case from http://getbootstrap.com/docs/4.0/getting-started/javascript/#programmatic-api it seems weird that we do it here but not everywhere else in the docs (randomly checking other pages, we seem to stick to the documented methods as written on those pages). As this isn't properly explained as is, and as it adds nothing (more of a preference for authors), it would be easier to just drop the variant and stick with the documented method as outlined later on in the same page (avoids having to go off on a "why should you use this instead of that" tangent here).
* use descriptive docs btn naming
* rename `btn-bd-yellow` to `btn-bd-download`
* sort state vars
* sort state vars
* info, warning, danger
* rename btn-bd-purple
* rename `.btn-bd-purple` to `.btn-bd-primary`
* align docs color variables
* generate $bd-purple-light color
* with http://razorltd.github.io/sasscolourfunctioncalculator/
* allow overide of docs variables
