Highlighted

Integrating a modern frontend in a multi tenant AEM project (part 1) | AEM Community Blog Seeding

kautuk_sahni

Community Manager

26-06-2020

BlogImage.jpg

Integrating a modern frontend in a multi tenant AEM project (part 1) by Natalia Venditto

Abstract

Tech stack
I will presuppose that the whole project is structured following the Maven Archetype https://maven.apache.org/guides/introduction/introduction-to-archetypes.html (or the Adobe Archetype, in the best of cases), and obviously, that Maven is the compilation tool to put it together. Other assumptions, you're using at least version 6.3 of AEM, Maven 3.5+, Java8, and Sling Models. (Although the backend tech matters little, to be honest, the Maven version does not)

Folder Structure
The first thing you need to consider, is your folder structure. And to decide your folder structure, you may need to work together with your backend tech leads or solution architect.

Clientlibs
If you've been working with AEM for a while, as a frontend or backend developer, you're very likely familiar with AEM's pattern for frontend code, the client-side libraries (known by AEM devs as clientlibs). You can read more about them here -> https://helpx.adobe.com/experience-manager/6-4/sites/developing/using/clientlibs.html

Read Full Blog

Integrating a modern frontend in a multi tenant AEM project (part 1)

Q&A

Please use this thread to ask the related questions.

AEM AEMEBlogSeeding Experience Manager