Hi @AEMWizard  Please check https://experienceleaguecommunities.adobe.com/t5/edge-delivery-services-questions/aem-edge-delivery-service-cicd-pipelines-from-cloud-manager/td-p/724872 

Hi @AEMWizard  For EDS, its just github repo, no deployment using Adobe Cloud Manager. However if you want to use Adobe's CDN, then you might need to deploy CDN config using CI/CD but please check this with Adobe

Hi @AEMWizard  You can check below for forms option in EDS  https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/edge-delivery/build-forms/getting-started-edge-delivery-services-forms/create-forms  

Hi @AEMWizard  You need to Generate different Navigation for different locales, there is no OOTB multisite management in EDS. All depends on your Authoring tool capabilities, in case of core component its AEM, who does take care of adjusting content.   You need to build a plugin if you are using goo...

Hi @AEMWizard  In EDS, MSM it depends on your Authoring system i.e. Sharepoint, Google drive or AEM. If you are using document based authoring then you have to build/rely on sharepoint/google drive capabilities to generate the market/language specific content.

Hi @AEMWizard  No, you can rely on Adobe's Fastly CDN.

Yes.   AEM Code Sync listens to changes on your code repositories, publishes code to AEM's code bus for high availability and intelligently purges CDN caches when changes have been made.    https://github.com/apps/aem-code-sync 

Hi @AEMWizard  Currently no can't protect https://<branch>--<repo>--<owner>.aem.live but Adobe is working on this to provide any solution/workaround.   but yes you need to map https://<branch>--<repo>--<owner>.aem.live  to www.applepro.com Please check : https://experienceleaguecommunities.adobe.com...

Hi @AEMWizard  Please check helix architecture https://github.com/adobe/helix-home/blob/main/docs/architecture-v5.md    preview has no CDN caching so there won't be any issue due to caching. for live when you push the code, cache is flushed.

Hi @AEMWizard  Yes but generally for production different there would be a different git repo used to make sure prod has different content mapping and non-prod has different.   The prod git repo is the fork of non-prod git repo.   But Adobe has come up with another solution for this problem, that is...