Hi Sander.
So, if I understand your suggestions correctly, it would look something
like this:
*app-shell*
- shared navigation
- shared content
- index.html
- router-outlet
- to load in content from each (external) individual app (see below)
into the index.html
*App-A*
- content and functionality for App-A
*App-B*
- content and functionality for App-B
*App-C*
- content and functionality for App-C
In this scenario, each application would be in its own code-base, and teams
would only need to deploy their individual apps when making changes. The
only time the app-shell would need to get updated/deployed is if a new
route got added for new navigation, or new shared content got added. *Does
this summarize your suggestion correctly?*
Some questions:
- In the scenario described above, would each smaller app (i.e., non
app-shell) also be bootstrapped for Angular 2 individually, or would the
bootstrapping only happen on the app-shell?
- Will the router be able to handle loading content
(components/templates) from external apps?
Thanks again!
~Milad
On Wednesday, July 13, 2016 at 9:47:02 AM UTC-4, Sander Elias wrote:
>
> Hi Milad,
>
> Sure. Create an "app-shell" that hold the menu(s) and stuff that needs to
> be the same for each smaller app. You can then use the router inside the
> app for each part itself, and navigate between different apps like usual.
> You menu can be partly fixed, and partly dynamic, depending on your needs.
>
> Regards
> Sander
>
--
You received this message because you are subscribed to the Google Groups
"AngularJS" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.
