AEM Cloud Multi Brand Project | Community
Skip to main content
Jineet_Vora
Community Advisor and Adobe Champion
Jineet_VoraCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
May 2, 2023
Solved

AEM Cloud Multi Brand Project

  • May 2, 2023
  • 2 replies
  • 957 views

We have single AEM Cloud Program and we have a requirement to have 2 projects (multi-brand) with site-a and site-b. Both the sites would have some common components, services and few distinct as well.

 

Since AEM Cloud deployment is a docker image based, what is the recommended approach where different teams can work with different release cycles?

 

Adobe suggests Git Submodule https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/using-cloud-manager/managing-code/cloud-manager-repositories.html?lang=en#git-submodule-support but is there any disadvantage of using this approach? Any suggestion?

 

Thank you!

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 krati_garg

@jineet_vora You can have multiple projects as GIT sub modules. Different teams can work on their respective repositories, however, there should be a Syncing mechanism which will pull all the Content from multiple branches and add it to Cloud Manager GIT repository. 
Help document to build the syncing mechanism:
https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/using-cloud-manager/managing-code/working-with-multiple-source-git-repositories.html?lang=en


I believe if you have different release cycle for different projects, you might want to set up a governance model to ensure basic Sanity is being performed for all the projects, which are getting live with a project release

2 replies

krati_garg
Adobe Employee
krati_gargAdobe EmployeeAccepted solution
Adobe Employee
May 3, 2023

@jineet_vora You can have multiple projects as GIT sub modules. Different teams can work on their respective repositories, however, there should be a Syncing mechanism which will pull all the Content from multiple branches and add it to Cloud Manager GIT repository. 
Help document to build the syncing mechanism:
https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/using-cloud-manager/managing-code/working-with-multiple-source-git-repositories.html?lang=en


I believe if you have different release cycle for different projects, you might want to set up a governance model to ensure basic Sanity is being performed for all the projects, which are getting live with a project release

    Shubham_borole
    Community Advisor
    Shubham_boroleCommunity Advisor
    Community Advisor
    May 5, 2023

    Hi,


     For common services and components, a separate repo similar to Adobe's core component library can be created.

    Both project A and B can include core dependencies from custom Core project for utils, services etc. And for components we can use super resourcetype to extend components. 

      Terms & ConditionsAccessibility statement

      Loading footer...