Sorry, I forgot to mention that the CMS in case is AEM. On Thursday, October 26, 2017 at 7:55:31 AM UTC-4, forexleads wrote: > > Thanks for your reply. You have shared some interesting direction. I will > read up on it. Thanks for the guidance. > > On Wednesday, October 25, 2017 at 10:50:14 AM UTC-4, Zlatko Đurić wrote: >> >> >> >> On Tuesday, October 24, 2017 at 8:40:43 AM UTC+2, forexleads wrote: >>> >>> I am a content management architect looking for some guidance from the >>> Angular experts. Following is my thought process for a project. Please let >>> me if this is doable and recommended. >>> "For some pages, to deliver content between header and footer, my >>> Angular app will make API calls to the Content Management System and get >>> HTML content including Angular Components/Directives. These custom >>> components in turn are responsible for making API Calls to other systems >>> and presenting the final content and data to the user. Is this supportable >>> and an acceptable approach?" >>> >> >> In some ways it's feasible, but that depends. Which CMS are you talking >> about? >> >> Lazy-loading modules is working quite ok, and you don't even need an API >> for that, it's just about bundling the components of your app. >> >> If you're talking about getting fresh chunks of raw HTML code, that could >> work, but with more code and some workarounds. You might need to >> "rehidrate" the app later - e.g. if this custom html has some event >> bindings, you'll have to know which are these and reattach them. Have a >> component that knows how to. You might also wanna look into Angular >> Universal there. >> >>
-- You received this message because you are subscribed to the Google Groups "Angular and AngularJS discussion" 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.
