meanjs.org has a pretty good approach to this. Install meanjs. It comes with sigin / signup and even allows you to create articles from a vanilla installation.
Simply put, when you create a web application with the MEAN stack, think of AngularJS as the "THE" application and node.js as the api. If you approach the creation of your web application as a javascript application (AngularJS), this happens to get your data from the api server (node.js), then you will begin to understand how to use the MEAN stack correctly.
First: Angular will have the routes defined in $ routeProvider . First create routing URLs in AngularJS. These are the "routes" for your web application. A good way to look at this is to create part of AngularJS with the ability to change your api server even in another language (PHP, python, go, etc.), if necessary.
Second: Create your AngularJS to communicate with api with $ resource . Essentially, $ resource is an easy way to access api using quiet routing. This "quiet routing" is now a routing that needs to be "simulated / copied" into routing for node.js. routes.
Often, AngularJS routes (url) will match the $ resource routing, which matches the node.js routing.
Take a look at meanjs.org again , and you will have a better understanding of how to properly organize what the "separate" (and actually) two separate applications are.
Jon
source share