What is the best practice for EDS when it comes language switcher exactly like how the AEM Core Components have implemented. Because EDS has no backend, how does the links get generated understand which path it needs to render?This is the AEM language switcher component, https://www.aemcomponents.de...

On an AEM Edge Delivery Service web site, we understand that the code is all frontend. As a current customer of AEMaaCS with a contract, and having 4 existing websites that serves on the platform. Adobe says using AEM Edge Delivery Service is free, so we wish to use this.While customers are surfing ...

While re-using the AEM tenant > program, we plan to push out an AEM Edge Delivery Service website, where does the Cloud Manager's CICD pipeline get kicked in? Should AEM Edge Delivery Service be rolled out via Adobe Cloud Manager Pipeline or will just pushing code to private repo to the Repository a...

What is the proper way to setup CDN for the Edge Delivery Service website? while using the feature "use this template", how can we add this to the AEMaaCS pipelines?And is it even suppose to be there, and so, how do we even setup Pipeline Config (this is cloud manager's CICD tool) https://github.com...

While adding images, mp4 (videos), pdfs, and other documents, how would content authors use the document base authoring to upload images like https://ext-images--franklin-assets-selector--hlxsites.hlx.page/external-images-example?view-doc-source=true, and are these saved into the dam?Our AEM custome...

Can someone please explain to me how do we install our Edge Delivery Website via production (https://<branch>--<repo>--<owner>.aem.live/) sites to live production, for example www.applepro.com. When it seems like https://<branch>--<repo>--<owner>.aem.live is the one that is serving the website, and ...

So once when we push code into main branch, how does the code get promoted to preview or live?For these environments, preview (https://<branch>--<repo>--<owner>.aem.page/) and production (https://<branch>--<repo>--<owner>.aem.live/) sites.

So, after following Adobe's tutorial on https://www.aem.live/developer/tutorial, we are ready to work on this on production.Here's what we have done, not sure if this is correct, but this is it.1. Create private repo from "use this template" feature found in https://www.aem.live/developer/tutorial2....

And so, how does https://main--mysite--aemtutorial.aem.live turn into https://www.mywebsite.com

I went through the tutorial, https://www.aem.live/developer/tutorial, and the tutorial has us share a folder to helix@adobe.com. Is this the same process on production?On the development documentation, it also says our github needs to be public and URLs are produced, https://<branch>--<repo>--<owner...