Fix labels from being blocked by content
Fixes #1541 — Disabled button beyond screen bounds

Fixes Issue #1541 — Settings > Indices disabled button expands beyond bounds on mobile.

This is done by saying that devices smaller than 768px should use normal whitespacing instead of nowrap.
[Fix Issue #1554] Set Max Width of Name Field

By setting the `max-width` of `.navbar > .name` we should be able to prevent issue #1554 from occurring and going beyond the bounds of the body.
adding vislib documentation
adding more YUI documentation
more YUI documentation
adding more YUI documentation
finishing YUI documentation, preparing for pr
Merge pull request #1563 from kkirsche/patch-2

[Fixes #1541] Disabled button beyond screen bounds
Merge pull request #1568 from kkirsche/patch-3

[Fix Issue #1554] Set Max Width of Name Field
Merge pull request #1535 from kkirsche/master

[Fixes #1534] Fix labels from being blocked by content
Add grunt dev to the dev environment setup process
Merge branch 'master' of github.com:elasticsearch/kibana
Add example pattern using kbn-info directive

Provide info based on verbage found in Logstash's elasticsearch output (http://logstash.net/docs/1.4.2/outputs/elasticsearch#index) documentation.
Provide clearer verbage
Isolate ruby environment and set java heap size

* Clear GEM_HOME and GEM_PATH variables to ensure we are only using
  the gems baked into the kibana jar and don't accidentally use
  the user/system's gem paths (Fixes #1531)
* Set JVM heap size to 512m. If we don't do this, the default (for the
  common JVMs) is 25% of system ram, which is not a desirable default.
[rootSearchSource] set the default index pattern properly on change
[config] log the proper values on change
[notifier] #event() respects returned vals, and promises
Show examples as help-block based on context

Based on @rashidkpc's feedback — display example / help text underneath the label as a help block allowing the user to more easily utilize the data inside of it.