AngularJS + AEM | Community
Skip to main content
Level 2
October 16, 2015
Solved

AngularJS + AEM

  • October 16, 2015
  • 6 replies
  • 2433 views

Hello

My team is considering using AngularJS with AEM implementation.  I could very much use a little info on the compatibility of AngularJS with AEM.

Apparently my team previously worked on a POC using AngularJS with CQ5 and the outcome was CQ’s WSIWYG editor could not be easily used to author content with Angular.

 

Does AngularJS "play nice" with AEM 6 ?  Are there any compatibility issues with the 2 ?

Are there certain version of CQ / AEM that work or do not work with AngularJS ?

Thanks!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by smacdonald2008

Here is an AEM community article that talks about this use case:

http://helpx.adobe.com/experience-manager/using/AngularJS.html

6 replies

wimvandenbrande
October 16, 2015

Just posted an article on AEM 6 and AngularJS with a little more useful and practical example: http://wp.me/p24Mjq-nn

smacdonald2008
smacdonald2008Accepted solution
Level 10
October 16, 2015

Here is an AEM community article that talks about this use case:

http://helpx.adobe.com/experience-manager/using/AngularJS.html

smacdonald2008
Level 10
October 16, 2015

Its just another framework for Javascript. Make sure that you include your lib fies in a client lib like you would when using other JS frameworks like JQuery. We will look into the possibility of wring a community article based on this use case. 

smacdonald2008
Level 10
October 16, 2015

Upon further investigation, there does seem to be an issue. I am investigating this and will post back. 

smacdonald2008
Level 10
October 16, 2015

Angular works fine in Classic UI in AEM 6.

[img]Angular.png[/img]

I am investigating what needs to be done in Touch UI to get it working. 

smacdonald2008
Level 10
October 16, 2015

Just found out that there is a known issue when using this JS framework in Touch UI. I will release a community article on this next week and it will update the status of this known issue, No issue when working in classic view.