Build docpress docs

.travis.yml

@@ -6,5 +6,18 @@ node_js:
 #   - node_modules
 #   - fixtures
 sudo: false
+script:
+- npm test
+- ./node_modules/.bin/docpress build
+after_success:
+- if [ "$TRAVIS_BRANCH" = "master" -a "$TRAVIS_PULL_REQUEST" = "false" ]; then ./node_modules/.bin/git-update-ghpages -e; fi
+cache:
+  directories:
+  - node_modules
 env:
+  global:
   - CC=clang CXX=clang++ npm_config_clang=1
+  - GIT_NAME: Travis CI
+  - GIT_EMAIL: nobody@nobody.org
+  - GITHUB_REPO: rstacruz/pnpm
+  - GIT_SOURCE: _docpress

docs/vs-npm.md

@@ -12,6 +12,7 @@ npm performs its action in stages. That is, it performs one stage for all depend
 
 - Resolving: get package data and what dependencies it has. (high requests, low bandwidth)
 - Fetching: fetch module contents (low requests, high bandwidth)
+- Extracting: extracting module contents from .tar.gz (no network IO)
 - Building: build compiled modules (no network IO)
 
 On the other hand, pnpm will eagerly move onto the next stage for a module even if other modules are stuck in earlier stages. This allows you to pnpm to more efficiently manage network IO: for instance, it can build compiled modules in the background while resolutions/fetches are still happening.

package.json

@@ -41,9 +41,11 @@
     "throat": "2.0.2"
   },
   "devDependencies": {
+    "docpress": "0.6.10",
     "eslint": "1.10.3",
     "eslint-config-standard": "4.4.0",
     "eslint-plugin-standard": "1.3.1",
+    "git-update-ghpages": "1.3.0",
     "nixt": "0.5.0",
     "npm": "3.6.0",
     "sepia": "2.0.1",