In the below page near the top the writer does a good job of describing all the puzzle pieces Angular makes up in a web app, but there was just one that I wasn't able to find a good source of information on:
Everything you need to build a CRUD app in a cohesive set: data-binding, basic templating directives, form validation, routing, deep-linking, reusable components, dependency injection.
Routing in AngularJS (at least as far as I've understand) refers to the action of taking a URL in the browser, and mapping that to a controller and view.
For instance, you can set up that the url:
/admin runs the
AdminCtrl-controller and loads the view
/partials/admin.html. When I say load view, I don't mean that the browser refreshes to the page
/partials/admin.html, rather it loads it in the background (using AJAX I presume, or an IFrame, or some other means of acquiring it), and when it has the data it compiles it (as angular does with the page), and runs it against the scope given to the
AdminCtrl-controller. It then inserts the result into any
ng-view-directive on the page.