From 42c89b1b9bd750366e699d3fde6bb2f43c4f1c1a Mon Sep 17 00:00:00 2001 From: vsavkin Date: Fri, 17 Jun 2016 09:17:48 -0700 Subject: [PATCH] docs(router): add a README to include a link to the guide --- modules/@angular/router/README.md | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/modules/@angular/router/README.md b/modules/@angular/router/README.md index b2cd4b361f..df1f0c61d3 100644 --- a/modules/@angular/router/README.md +++ b/modules/@angular/router/README.md @@ -1,7 +1,12 @@ -# Router +Angular Route +========= Managing state transitions is one of the hardest parts of building applications. This is especially true on the web, where you also need to ensure that the state is reflected in the URL. In addition, we often want to split applications into multiple bundles and load them on demand. Doing this transparently isn’t trivial. -The Angular router is designed to solve these problems. Using the router, you can declaratively specify application state, manage state transitions while taking care of the URL, and load components on demand. In this article I will discuss the API of the router, as well as the mental model and the design principles behind it. +The Angular router is designed to solve these problems. Using the router, you can declaratively specify application state, manage state transitions while taking care of the URL, and load components on demand. -Read the in-depth overview of the Router [here](http://victorsavkin.com/post/145672529346/angular-router). \ No newline at end of file +## Overview +Read the overview of the Router [here](http://victorsavkin.com/post/145672529346/angular-router). + +## Guide +Read the dev guide [here](https://angular.io/docs/ts/latest/guide/router.html). \ No newline at end of file