Expand my Community achievements bar.

Submissions are now open for the 2026 Adobe Experience Maker Awards.
SOLVED

How to utilize EDS with an existing AEM Cloud site?

Avatar

Level 7

I already have a site running on AEM Cloud that was created a couple of years ago using the standard author and publisher flow. The site has multiple pages that are working fine.

Now I want to integrate and utilize Edge Delivery Services (EDS) with this existing site and its pages.

I have already gone through https://experienceleague.adobe.com/en/docs/events/experience-manager-gems-recordings/gems2024/aem-au... It says that a new site needs to be created and a GitHub repository must be linked to it, after which I can add pages to that new site. But what happens to the pages that already exist in other sites? Do I have to manually migrate all the pages from site XYZ (built using the standard author and publisher flow) to the new site ABC?

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @AnkitJasani29 ,

I believe the site pages you created years ago were built using standard AEM, with typical AEM components and templates, and the same applies to the code structure.

When working with EDS, we use all the new features, including its own template, OOTB blocks, and site pages that are compatible with the Universal Editor. The old pages will not open in the Universal Editor. EDS also has a separate GitHub repository where the blocks are stored, whereas your old pages rely on the older components.

Therefore, it is recommended to manually create all the pages by following the EDS development guidelines.

View solution in original post

1 Reply

Avatar

Correct answer by
Community Advisor

Hi @AnkitJasani29 ,

I believe the site pages you created years ago were built using standard AEM, with typical AEM components and templates, and the same applies to the code structure.

When working with EDS, we use all the new features, including its own template, OOTB blocks, and site pages that are compatible with the Universal Editor. The old pages will not open in the Universal Editor. EDS also has a separate GitHub repository where the blocks are stored, whereas your old pages rely on the older components.

Therefore, it is recommended to manually create all the pages by following the EDS development guidelines.