Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

Major issues faced while using Angular2 with AEM

Avatar

Level 2

Hi ,

we are starting a new project and we are not sure whether to go with angular1.6 or angular2. I have gone through few adobe links and they stated few issues with angular2 like:

Please help me clarify whether to go for angular2 or not.

1 Accepted Solution

Avatar

Correct answer by
Level 3

I think it depends on what you're building. A single page app should work fine with Angular and AEM. If you are letting content creators make pages then it depends on that components. Most components don't require more than a JSP or HTL. If you need something more dynamic or interactive then I've had success with Vue.js and x-tag libraries. I should note that I also tend to avoid HTL, so your experience may be different.

View solution in original post

3 Replies

Avatar

Level 10

The idea component language is HTL. Adding 3rd party JS libs to AEM can be achieved; however, you have to determine which 3rd party libs best suit your project.

I have asked a few internal ppl that use different libs to look at this thread and give their view. 

Avatar

Level 2

Thanks scott.

we are using adobe target as well and in few links they have mentioned issues with that also. please help us choose the right framework so that later down the line we don't have to start over if we face major issues.

Avatar

Correct answer by
Level 3

I think it depends on what you're building. A single page app should work fine with Angular and AEM. If you are letting content creators make pages then it depends on that components. Most components don't require more than a JSP or HTL. If you need something more dynamic or interactive then I've had success with Vue.js and x-tag libraries. I should note that I also tend to avoid HTL, so your experience may be different.