add gh-pages make command, added live demo

Makefile

@@ -6,6 +6,7 @@ browserify = $(bin)/browserify
 exorcist = $(bin)/exorcist
 eslint = $(bin)/eslint
 http-server = $(bin)/http-server
+gh-pages = $(bin)/gh-pages
 mocha = $(bin)/mocha
 mocha-phantomjs = $(bin)/mocha-phantomjs
 node = node
@@ -42,6 +43,10 @@ dist: $(shell find ./lib) package.json
 examples:
 	@ $(browserify) $(browserify_flags) ./examples/index.js --outfile ./examples/build.js
 
+# Deploy the latest examples to GitHub pages.
+gh-pages:
+	@ $(gh-pages) --dist ./examples
+
 # Install the dependencies.
 install:
 	@ npm install

Readme.md

@@ -5,10 +5,10 @@
 <p align="center">A <em>completely</em> customizable framework <br/>for building rich text editors in the browser.</p>
 <br/>
 
-<p align="center"><a href="#why"><strong>Why?</strong></a> · <a href="#principles"><strong>Principles</strong></a> · <a href="#examples"><strong>Examples</strong></a> · <a href="#plugins"><strong>Plugins</strong></a> · <a href="#documentation"><strong>Documentation</strong></a> · <a href="./Contributing.md"><strong>Contributing!</strong></a></p>
+<p align="center"><a href="#why"><strong>Why?</strong></a> · <a href="#principles"><strong>Principles</strong></a> · <a href="https://ianstormtaylor.github.io/slate"><strong>Demo</strong></a> · <a href="#examples"><strong>Examples</strong></a> · <a href="#plugins"><strong>Plugins</strong></a> · <a href="#documentation"><strong>Documentation</strong></a> · <a href="./Contributing.md"><strong>Contributing!</strong></a></p>
 <br/>
 
-<p align="center"><a href="#"><img src="./docs/images/preview.png"></a></p>
+<p align="center"><a href="https://ianstormtaylor.github.io/slate"><img src="./docs/images/preview.png"></a></p>
 
 <p align="center"><a href="https://www.npmjs.com/package/slate"><img src="https://img.shields.io/npm/dt/localeval.svg?maxAge=2592000"></a> <a href="https://slate-slack.herokuapp.com"><img src="https://slate-slack.herokuapp.com/badge.svg"><a/></p>
 <br/>
@@ -60,6 +60,12 @@ Slate tries to solve the question of "[Why?](#why)" with a few principles:
 7. **Clear "core" boundaries.** With a plugin-first architecture, and a schema-less core, it becomes a lot clearer where the boundary is between "core" and "custom", which means that the core experience doesn't get bogged down in edge cases.
 
 
+<br/>
+### Demo
+
+Check out the [**live demo**](https://ianstormtaylor.github.io/slate) of all of the examples!
+
+
 <br/>
 ### Examples
 

package.json

@@ -39,6 +39,7 @@
     "eslint-plugin-import": "^1.10.2",
     "eslint-plugin-react": "^5.2.2",
     "exorcist": "^0.4.0",
+    "gh-pages": "^0.11.0",
     "http-server": "^0.9.0",
     "mocha": "^2.5.3",
     "mocha-phantomjs": "^4.0.2",