Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

How to build a new SPA app into and existing AEM cloud project/site, one code base...

Avatar

Level 1

Our site-project has recently been transformed and moved into the AEM Cloud.  I want to create a SPA app within this existing project.  I see the tutorials how to create a SPA project that connects and uses AEM but how to integrated it in to one code base for deployments is my hang up.      I'm thinking this may not be possible or desired, especially if we want to create more AEM SPA apps.  I just don't know how to integrated this all together to be hosted on our AEM Sites Cloud project instance.

 

Thank you for any articles or guidance.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @Zidu ,

 

We can have more than one project in our codebase and it needs to be embedded in all container package.

 

For example, a complex deployment content package structure might look like this:

  • all content package embeds the following packages, to create a singular deployment artifact
    • common.ui.apps deploys code required by both site A and site B
    • site-a.core OSGi bundle Jar required by site A
    • site-a.ui.apps deploys code required by site A
    • site-a.ui.config deploys OSGi configurations required by Site A
    • site-a.ui.content deploys content and configuration required by site A
    • site-b.core OSGi bundle Jar required by site B
    • site-b.ui.apps deploys code required by site B
    • site-b.ui.config deploys OSGi configurations required by site B
    • site-b.ui.content deploys content and configuration required by site B

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/develo... 

View solution in original post

1 Reply

Avatar

Correct answer by
Community Advisor

Hi @Zidu ,

 

We can have more than one project in our codebase and it needs to be embedded in all container package.

 

For example, a complex deployment content package structure might look like this:

  • all content package embeds the following packages, to create a singular deployment artifact
    • common.ui.apps deploys code required by both site A and site B
    • site-a.core OSGi bundle Jar required by site A
    • site-a.ui.apps deploys code required by site A
    • site-a.ui.config deploys OSGi configurations required by Site A
    • site-a.ui.content deploys content and configuration required by site A
    • site-b.core OSGi bundle Jar required by site B
    • site-b.ui.apps deploys code required by site B
    • site-b.ui.config deploys OSGi configurations required by site B
    • site-b.ui.content deploys content and configuration required by site B

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/develo...