update docs

Author: yyx990803

docs/SUMMARY.md

@@ -26,3 +26,4 @@
   - [router.redirect](api/redirect.md)
   - [router.alias](api/alias.md)
   - [router.beforeEach](api/before-each.md)
+  - [router.afterEach](api/after-each.md)

docs/api/README.md

@@ -10,3 +10,4 @@
 - [router.redirect](redirect.md)
 - [router.alias](alias.md)
 - [router.beforeEach](before-each.md)
+- [router.afterEach](after-each.md)

docs/api/after-each.md

@@ -0,0 +1,21 @@
+# `router.afterEach(hook)`
+
+Set the global after hook, which will be called every time when a route transition successfully **enters the activation phase**.
+
+Note this hook being called only means the transition has been validated, i.e. all `canDeactivate` and `canActivate` hooks have successfully resolved and the browser URL has been updated. It does not guarantee that all `activate` hooks have been resolved.
+
+You can only have one global after hook at a time; however you can implement your own middleware system inside this hook.
+
+### Arguments
+
+- `hook {Function}`
+
+  The hook function receives a single argument which is a [Transition Object](../pipeline/hooks.html#transition-object), but you can only access its `to` and `from` properties, which are route objects. You **cannot** call transition methods in the global after hook.
+
+### Example
+
+``` js
+router.afterEach(function (transition) {
+  console.log('Successfully navigated to: ' + transition.to.path)
+})
+```

docs/api/on.md

@@ -5,7 +5,7 @@ Add a single root-level route configuration. Internally, `router.map()` simply c
 ### Arguments
 
 - `path: String` - see [Route Matching](../route.md#route-matching)
-- `config: Object` - see [Route Config Object](map.html#route-config-object).
+- `config: Object` - see [Route Config Object](map.md#route-config-object).
 
 ### Example
 

docs/pipeline/activate.md

@@ -4,7 +4,7 @@ Called on an incoming component during the activation phase when it is created a
 
 ### Arguments
 
-- [`transition {Transition}`](hooks.html#transition-object)
+- [`transition {Transition}`](hooks.md#transition-object)
 
   Call `transition.next()` to resolve the hook. Note calling `transition.abort()` here will not take the app back to the previous route because the transition has already been validated.
 

docs/pipeline/can-activate.md

@@ -4,7 +4,7 @@ Called on an incoming component during the validation phase.
 
 ### Arguments
 
-- [`transition {Transition}`](hooks.html#transition-object)
+- [`transition {Transition}`](hooks.md#transition-object)
 
   Call `transition.next()` to resolve the hook. Calling `transition.abort()` will invalidate and cancel the transition.
 

docs/pipeline/can-deactivate.md

@@ -4,7 +4,7 @@ Called on a leaving component during the validation phase.
 
 ### Arguments
 
-- [`transition {Transition}`](hooks.html#transition-object)
+- [`transition {Transition}`](hooks.md#transition-object)
 
   Call `transition.next()` to resolve the hook. Calling `transition.abort()` will invalidate and cancel the transition.
 

docs/pipeline/can-reuse.md

@@ -6,7 +6,7 @@ This route options can either be a plain Boolean value, or a function that synch
 
 ### Arguments
 
-- [`transition {Transition}`](hooks.html#transition-object)
+- [`transition {Transition}`](hooks.md#transition-object)
 
   You can only access `transition.to` and `transition.from` in a `canReuse` hook.
 

docs/pipeline/data.md

@@ -4,7 +4,7 @@ Called on an incoming component during the activation phase, after the `activate
 
 ### Arguments
 
-- [`transition {Transition}`](hooks.html#transition-object)
+- [`transition {Transition}`](hooks.md#transition-object)
 
   Calling `transition.next(data)` will set each property in `data` on the component. For example, with `{ a: 1, b: 2 }`, the router will call `component.$set('a', 1)` and `component.$set('b', 2)`.
 

docs/pipeline/deactivate.md

@@ -4,7 +4,7 @@ Called on a leaving component the activation phase when it is about to be deacti
 
 ### Arguments
 
-- [`transition {Transition}`](hooks.html#transition-object)
+- [`transition {Transition}`](hooks.md#transition-object)
 
   Call `transition.next()` to resolve the hook. Note calling `transition.abort()` here will not take the app back to the previous route because the transition has already been validated.
 

docs/pipeline/hooks.md

@@ -33,7 +33,7 @@ Each transition hook will receive a `transition` object as the only argument. Th
 
 - **transition.from**
 
-  A [route object](../route.html) representing the route we are transitioning from.
+  A [route object](../route.md) representing the route we are transitioning from.
 
 - **transition.to**
 
@@ -90,7 +90,7 @@ route: {
 }
 ```
 
-We are asynchronously fetching data in the `activate` hook here just for the sake of an example; Note that we also have the [`data` hook](data.html) which is in general more appropriate for this purpose.
+We are asynchronously fetching data in the `activate` hook here just for the sake of an example; Note that we also have the [`data` hook](data.md) which is in general more appropriate for this purpose.
 
 **TIP:** if you are using ES6 you can use argument destructuring to make your hooks cleaner:
 

package.json

@@ -13,7 +13,8 @@
     "e2e-sauce": "nightwatch -c build/nightwatch.sauce.json -e chrome,firefox,ie10,ie11",
     "e2e-local": "bash ./build/e2e.sh",
     "release": "bash ./build/release.sh",
-    "docs": "bash ./build/update-docs.sh",
+    "docs": "cd docs && gitbook serve",
+    "deploy-docs": "bash ./build/update-docs.sh",
     "test": "npm run lint && npm run unit && npm run e2e-local"
   },
   "repository": {