Different Target and Experience Platform environment under one AEM project | Community
Skip to main content
Michael_Soprano
Michael_Soprano
Level 10
November 8, 2023

Different Target and Experience Platform environment under one AEM project

  • November 8, 2023
  • 1 reply
  • 543 views

Hi, 

 

I would like to have two different demo websites:

  1. horeca industry demo 
  2. basic retail demo 

That would be under one AEM project and they would be using same components but with different visuals. 

I have heard that is possible... Could somebody confirm? 🙂 

However I am curious if I can use different instances of Target and Experience Platform?

It would be helpful for creating proof of concepts for customers with different industries.

 

Regards 

Mike 

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

1 reply

Preetpal_Bindra
Community Advisor
Preetpal_BindraCommunity Advisor
Community Advisor
November 8, 2023

Hello @michael_soprano ,

One AEM installation can support multiple websites if that is what you inferred from "one AEM project".

If the folder structure is chosen and implemented carefully, then multiple websites could also be nested under one area of AEM too.

 

Components can be certainly shared across both.

There are a few ways to achieve different visuals,

1. AEM Style system 

Link: https://experienceleague.adobe.com/docs/experience-manager-65/authoring/siteandpage/style-system.html?lang=en

 

2. One master component library as an independent AEM project, where all global components can be hosted and used across multiple sites.

 

3. Different stylesheets for every site can be applied to the page's template.

 

4. Context aware configurations could also be used to switch to stylesheets based on which website is being used.

Link: https://experienceleague.adobe.com/docs/experience-manager-core-components/using/developing/context-aware-configs.html?lang=en 

 

5. Core component library available to all AEM customers could be leveraged for using them as-is or extending them for custom use cases.

Link: https://experienceleague.adobe.com/docs/experience-manager-core-components/using/introduction.html?lang=en 

 

 

When it comes to using multiple Target and Experience platforms for different sites, that too is possible via a Tag management system (best practice) or implementing different scripts to connect Target/Experience Platform with AEM. Since, this is a custom need to switch between multiple systems, the solution will be custom implementation too.

 

regards,

Preetpal

Terms & ConditionsAccessibility statement

Loading footer...