From 503b07f698a6ad0026d8a3420a7b9c993632232b Mon Sep 17 00:00:00 2001 From: vsavkin Date: Thu, 9 Jun 2016 14:57:50 -0700 Subject: [PATCH] docs(router): add a README --- modules/@angular/router/README.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/modules/@angular/router/README.md b/modules/@angular/router/README.md index 7c4fbbaa59..b2cd4b361f 100644 --- a/modules/@angular/router/README.md +++ b/modules/@angular/router/README.md @@ -1 +1,7 @@ # Router + +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. + +Read the in-depth overview of the Router [here](http://victorsavkin.com/post/145672529346/angular-router). \ No newline at end of file