Single Page Apps (SPAs) aren't really intended to be used the way that you're suggesting with a really large application and multiple mini-SPAs within the main one. The biggest problem will be page load times as everything has to be loaded up front.

One way to tackle this is using a navigation page that will take you to individual SPAs. The navigation page will be fairly lightweight, and then you'll only load one SPA at a time based upon what was selected. You can provide a link bar with navigation links within each of your SPAs so users don't always have to go back to the navigation page when they need to go to another area.

Using this approach can create some challenges with persisting information across SPAs. But we're talking about something SPAs weren't intended to do. There are some frameworks that can help with client side data persistence. Breeze is the first that comes to mind, but there are others.

Regarding layout - several Programmers questions address large project layout, depending upon your particular needs. I came across this one and this one. There is nothing magical about SPAs that would affect your application layout beyond what is already answered in those questions.

That said, there are differing approaches that work best for different projects. I would recommend sticking with the base layout as provided by the angular seed project. Create separate folders from the provided ones for your custom packages and source code. And within your source folder, use a project layout that makes sense for your needs.

Single Page Apps (SPAs) aren't really intended to be used the way that you're suggesting with a really large application and multiple mini-SPAs within the main one. The biggest problem will be page load times as everything has to be loaded up front.

One way to tackle this is using a navigation page that will take you to individual SPAs. The navigation page will be fairly lightweight, and then you'll only load one SPA at a time based upon what was selected. You can provide a link bar with navigation links within each of your SPAs so users don't always have to go back to the navigation page when they need to go to another area.

Using this approach can create some challenges with persisting information across SPAs. But we're talking about something SPAs weren't intended to do. There are some frameworks that can help with client side data persistence. Breeze is the first that comes to mind, but there are others.

Regarding layout - several Programmers questions address large project layout, depending upon your particular needs. I came across this one and this one. There is nothing magical about SPAs that would affect your application layout beyond what is already answered in those questions.

That said, there are differing approaches that work best for different projects. I would recommend sticking with the base layout as provided by the angular seed project. Create separate folders from the provided ones for your custom packages and source code. And within your source folder, use a project layout that makes sense for your needs.