Adobe Experience Manager Edge Delivery Services

So for AEMaaCS, out of the box, these websites are closely coupled to fastly CDN and cannot be removed. While looking at the aem.live website for launch, https://www.aem.live/docs/byo-cdn-fastly-setup, it says that BYO CDN needs to be configured... does this mean that we need to pay for another CDN just to have a Edge Delivery Service running on production?

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. Next, install the AEM Code Sync GitHub App3. Create Folder on Google Drive Enterprise4. Share the Google Drive to helix@adobe.com5. Once when this step is done, will we be able to access the url from:preview (https://<branch>--<repo>--<owner>.aem.page/) and production (https://<branch>--<repo>--<owner>.aem.live/) sitesAre these the correct steps to setup Edge Delivery Services Production website?

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.

I am trying to do the local setup for xwalk project. I have completed the following steps:1. Running AEM instance in https mode.2. Running Universal Editor Service locally on port 80003. "aem up" in port 30004. created a site using "site from template"...and finally I have added the following meta tags in head.html :           <meta name="urn:adobe:aue:system:aemconnection" content="xwalk:https://localhost:8443">          <meta name="urn:adobe:aue:system:fcsconnection" content="fcs:https://example.franklin.adobe.com/345fcdd">          <meta name="urn:adobe:aue:config:service" content="https://localhost:8000">When i try to edit  the "index" page using the following url : https://experience.adobe.com/#/aem/editor/but when i preview the page and right click view source, it shows the "urn:adobe:aue:system:aemconnection" as "xwalk:http://localhost:4502". I am not able to save edi

Hey guys,  Working on an EDS Document based website, but I want to know if I can connect it to Hubspot / Salesforce integrations. I want to direct the form responses to some integrations etc. What is the best way? Thanks

While working on AEM and AEMaaCS, there is a tool where we can set aliases where the URL path is different, but the internal paths are the same. Is there some feature like this?

We are a customer on AEMaaCS and we can enable AEM Edge Delivery Service on our tenant, but from watching this video on 16:26, https://youtu.be/xTm4neB63ak?si=ITqgWPT0A0pIA8Iy&t=986, #1 is there a custom portal or UI for AEM Edge Delivery Service websites#2 how do we enable AEM sidekick, as seen in the video https://youtu.be/xTm4neB63ak?si=ITqgWPT0A0pIA8Iy&t=986, I see it here, https://www.aem.live/docs/sidekick-extension, but what happens if the repository is locked down as a private repo... how does adobe read this repository?

I wanted to create a site "pocfeature2site" using "create site config" Admin API. In Payload, I have mentioned the content as follows : "content": { "source": { "url": "https://author-blabla-.adobeaemcloud.com/bin/franklin.delivery/%7Borgname%7D/pocfeature2site/poc-feature2", "type": "markup", "suffix": ".html" } }In the URL section, I mentioned the site name after org name. Is it correct or we should mention the repository name only?

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>.aem.page/ In the example above that’s https://main--mysite--aemtutorial.aem.page/, but how about production... how are these links generated for production websites?

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 customer has a contract with AEMaaCS for 4 years, and its free to use EDS, just wondering where are the images actually placed.

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/adobe/aem-boilerplate this does not have any CICD pipeline cdn configuration code. 

For Edge Delivery Services, how do we perform multisite manager, say for example we havewww.applepro.com/ca/fr/home.htmlwww.applepro.com/ca/en/home.htmlwww.applepro.com/us/en/home.htmlwww.applepro.com/us/es/home.htmlWe are using document authoring.For example given that we are working on a large website like www.volvotrucks.com, how does their website create so many different market's and languages? https://www.volvotrucks.com/en-en/select-market.html 

 I want to leverage the repo less approach for my new EDS cross walk project, where four developers will be working collaboratively. Each developer will create their own feature branch in GitHub. Before merging their changes into the dev branch, they need to test their individual features separately.In the repo less documentation, Adobe mentions that it is possible to create multiple sites within a single repository. If we want to create a site for our cross walk project, what should be specified in the Content Source URL?Additionally, how can we configure the setup to allow each developer to test their features independently on their respective branches?  

My client is already having a few sites on AEM as a Cloud Service platform. They wish to bring in few more sites now on to the platform, but with EDS and UE features enabled along with Document Based Authoring. As obvious, their existing sites are all based on Editable Templates & Sightly Components. I plan to instrument those components for Universal Editor. But here are a few questions I have in my mind - How do the content editors author new EDS blocks/sections on those normal AEM Sites pages given that those site pages were not developed on EDS Site template and are based on parsys from drag-n-drop which UE does not recognize. Even on editing all such pages (2000+) from AEM Sites Console, Universal Editor does not open up automatically.How does the blocks created on Google Doc / Word documents map to the blocks that we will be developing on EDS client-side codebase so that once the pages are created using Document based authoring, Content Editors can edit them further

Is there any official Adobe documentation on working with a repoless setup for XWalk projects? Specifically, I want to use a single repository while managing different content sources for various feature branches. Is there any guide that explains handling multiple branches and multiple content sources effectively?

when i am running  the aem up command it showing the spanwn UNKNOWN error due to which localhost:3000 is not opening up. what could be the reasons behind this error. can anyone tell me how to resolve it. 

ContextI want to implement Universal Editor and Edge Delivery Services for our client who is using AEM as a Cloud Service. I am new to EDS and UE and have a few queries when it comes to implementing these on a real delivery project. Queries On my local AEMaaCS SDK, I copy the link of a page in "View as Published" mode, go to Universal Editor UI and put in the https page link. Is there a way that I select the page on AEM Sites Console and click on Edit, and the page gets opened on Universal Editor interface ? Reason is, I do not want the client to copy page URL and manually go to Universal Editor to paste it and then open the page on Universal Editor. I am aware of an Adobe documentation which says selecting a page and clicking on Edit opens the page on Universal Editor. That is not happening OOTB for me atleast on my local AEMaaCS SDK for a page where I have enabled a few components for Universal Editor. Is there any configuration that needs to be done to make it happen ?&nbs

Problem : No separate instance for UAT or QA, frequent changes, leading to defect leakage and inconsistent results. Ask : In EDS if there needs to be a dedicated QA environment or an UAT instance to test features and enhancements in isolation , is this achievable?Be it doc based authoring or xwalk how can this be achieved?Can docker or any other systems be used?  Note : there may be integration with other systems such as commerce , analytics,etc

Hi All, I am working on EDS locally. I have created my repository from boilerplate code.In my google drive, i have created one home page (google doc with just some texts) parallel to index, nav and footer page, but when i am trying to preview that home page it is rendering fine in main-eds link but upon hitting http://localhost:3000/home, header is loading fine and below i am getting 404 and footer is also not loading in homepage.if i am separately hitting footer, nav and index in 3000, they are loading fine.What can be the issue?  I have already updated my fstab.yml file in my local. Case is different when I am creating the repo myself. Everything is working as expected in that case.   

Hi Team, We are doing a POC, to integrate AEMaaCS with EDS. We have followed instructions as in https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/edge-delivery/wysiwyg-authoring/edge-dev-getting-started .1. When we publish the Page from AEM, we don't see page in EDS, rather seeing 404 error: 2. When we checked in AEM log after publishing the page, In the author-distribution agent logs we see 401 error for first request and then 404 error for second request to the helix/eds server as in the below screenshot: 3. Only configuration change are in fstab.yml with AEM mounting end point and path.json with mapping content pathCan please share your thoughts on this issue or potential fixes?Thanks!Chaithanya

Hi, I am able to integrate content fragment with a normal project by instrumenting it and making it capable of editing in the universal editor, now I want to achieve the same with the xwalk project created using the boilerplate: https://github.com/adobe-rnd/aem-boilerplate-xwalkI want to include content fragments and edit them using the universal editor itself.currently, I am including it as : component-models.json {"id": "calender-cf""fields": [{"component": "text","valueType": "string","name": "city","label": "enter the city",},{"component": "text","valueType": "string","name": "state","label": "enter the state",}]} component-definition.json{"title": "calender-cf","id": "calender-cf","plugins": {"aem":{"page": {"resourceType": "wknd/components/contentfragment"}}}}please help me on how it can be achievedThank you cc : @arunpatidar 

I created an EDS site using the "AEM Site with Edge Delivery Services Template 0.0.16" and set up configurations and headers within it. The paths.json file in the repository has the necessary mappings. I can access the Helix config via https://main--***.aem.page/config.json, but any updates made and republished do not show up in the config.json. Additionally, when attempting to load headers.json via https://main--**.aem.page/headers.json, I receive a 404 error. Please see the screenshots. 

I have created an EDS site using the "AEM Site with Edge Delivery Services Template 0.0.16" and set up configurations and headers within it. The paths JSON file in the repository has the necessary mappings. I can access the Helix config via main--**.aem.page/config. json, but any updates made and republished do not show up in the config JSON. Additionally, when attempting to load headers JSON via main--**.aem.page/headers. json, I receive a 404 error. @arunpatidar 

I have created an EDS site using the "AEM Site with Edge Delivery Services Template 0.0.16" and set up configurations and headers within it. The paths JSON file in the repository has the necessary mappings. I can access the Helix config via https://main--***.aem.page/config.json, but any updates made and republished do not show up in the config JSON. Additionally, when attempting to load headers JSON via https://main--**.aem.page/headers.json, I receive a 404 error.  Please let me know why the headers json I am not able to view.  @arunpatidar 

Dear adaptTo() Community,3 weeks after the adaptTo() developer conference for AEM and the related OSS projects - including a lot of talks around Edge Delivery Services - we have published all talk videos together with slides and Q&A: https://adapt.to/2024/scheduleimage gallery of the event: https://adapt.to/2024/conference/galleryand finally, the aftermovie: https://youtu.be/hC8gqorecQoSee you next year!Best regards,The adaptTo() Team