Adobe Experience Manager Edge Delivery Services

Dear adaptTo() Community,Europe’s leading AEM Developer Conference is back! From September 29 to October 1, 2025, Berlin’s Kulturbrauerei will once again bring together developers, architects, and tech enthusiasts for three days of knowledge-sharing, networking, and innovation.Ticket sales are open – Get your spot now!Call for Papers is live – Share your insights with the community!Loyalty Tickets available for previous attendees.Early Bird pricing until May 31, 2025 – Save before prices go up!Early Bird Tickets: https://adapt.to/ticketsCall for Papers – submit your talk by April 6, 2025: https://adapt.to/cfpYour adaptTo() Conference Team

Hey guys, Hope everyone is doing well. I am wondering if there is a way to use multiple Sharepoint URLs for a single Github Repo. For example, I have this sharepoint URL in my main branch: mountpoints:/: https://mycompany.sharepoint.com/:f:/r/sites/WebsiteProjects/Shared%20Documents/website And this one in my staging branch: mountpoints:/: https://mycompany.sharepoint.com/:f:/r/sites/WebsiteProjects/Shared%20Documents/staging Is it possible to do this? The use case for this is that we might need to separate out the content sources for different environments. Has anyone done this before? Thanks.

Hey Everyone, Context: Our team is currently trying to optimally setup a client's project, and we want to create a smooth CI/CD system which will take into account both the development side of contributions as well as the actual content authoring side (client side) of the flow. The tooling and process we're utilizing is as such (see attached screenshot as well of our current infra thinking & layout):- Document/Content Authoring & Asset Management = Sharepoint- Version Control and Development Organization = GitHub- Deployment and CDN = AEMaaCS (were using Edge Delivery) As for utmost safety in a project and to prevent unwanted mistakes, multiple environments should exist ideally. But so far this is understood by our team as such:- Feature branches take in local code changes/pushes- Merge into a Staging branch- Merge into QA or Main from which it goes to a production pipeline- The pipeline is triggered from main- Pipeline deploys to production (.com) site

Hey, we're building an EDS site for a client and ideally we don't want the .live or .page site to be crawlable or accessible publicly. We want some sort of security or VPN (or login) around it? Is this possible? What options do I have?

Hey everyone, We have an EDS website which we want to deploy on our AEM Cloud CDN using Edge Delivery Solution. (Screenshot below)I do understand the steps needed to configure and connect an EDS website to a Domain. However, this single domain instance will then be our production. I want a staging environment before in this pipeline, so it should somehow look like this:main----.aem.live ---> www.stagingURL.com ----> www.productionURL.com Is that pipeline possible in this configuration for EDS? What are the recommended best practices?  Thank you 🙂 

In my EDS Xwalk project, I want to add data attributes to individual dialog fields. For example, a text field includes default attributes like data-aue-prop="title", data-aue-label="Title", and data-aue-type="text". Similarly, if I want to add a new data attribute like data-field-id to specific dialog fields, what steps should I follow?

Hello!I've added a new plugin to Sidekick with a date picker.My goal is when a date is selected, to add the page we are on to the crontab.xlsx sheet and in the "when" column to have the selected date and in the "command" column to have the publish command.Does anyone know if that is possible? Do we have any examples of this? 

Hey everyone,  Note: main questions to address at bottom of post. This is a general question about the process for setting up DevOps CI/CD pipeline(s) via EDS. Really appreciate any help or guidance/tips on this, as I know this is a new process overall and many others may be in me and my teams shoes.Context: Our team is currently trying to optimally setup a client's project, and we want to create a smooth CI/CD system which will take into account both the development side of contributions as well as the actual content authoring side (client side) of the flow. The tooling and process we're utilizing is as such (see attached screenshot as well of our current infra thinking & layout):- Document/Content Authoring & Asset Management = Sharepoint- Version Control and Development Organization = GitHub- Deployment and CDN = AEMaaCS (we are using Edge Delivery) As for utmost safety in a project and to prevent unwanted mistakes, multiple environments should

Data ingestion and forms in EDS are depreciated (https://www.aem.live/developer/forms)Are there any other options for me to intake data through forms in EDS from users and store them somewhere within AEM or EDS?Thanks,Osman

Hey Team,We are trying to use the Edge Delivery Service GitHub template for our website to enable AEM Site Universal Editor authoring.Our approach is as follows: we have a Site_A repository, a Site_B repository, and a common repository. We would like to create a component in the common repository and use it in both Site_A and Site_B. Is this possible? If so, how can we achieve it?

This is a 2 part question regarding EDS handling of javascript and CSS. Part 1: AEM 6.5 has a feature that minifies javascript and CSS. Does EDS have a similar ability or is this an optimization step that must happen inside the GIT repo? Part 2: Adobe AEM Commons has a "Versioned Clientlibs" feature that adds a new cache-busting string to a file path when a clientlib is updated. Does EDS have a similar ability or is there some other process?

Hi Team Is it possible to have toggle button in the content fragment model. Could you please advise on the same.

I am writing to report an error we are experiencing while authoring adaptive forms in universal editor. Please find the below error occurs while trying to author Adaptive forms in universal editor, other:java.base/java.lang.Thread.run(Thread.java:1583), 2% HTTP-POST:/content/eds-poc3/forms/jcr:content/root/secti...] [CommitStats overhead was 2ms = 59.0us / commit]09.01.2025 23:20:00.655 [cm-p51328-e442308-aem-author-55577c4448-zb7sl] *ERROR* [13.113.45.32 [1736464799542] GET /content/eds-poc3/forms/jcr:content/root/section_727041587.html HTTP/1.1] com.day.cq.wcm.core.impl.WCMDeveloperModeFilter Error during include of SlingRequestPathInfo: path='/content/eds-poc3/forms/jcr:content/root/section_727041587/form_896591219', selectorString='null', extension='html', suffix='null' org.apache.sling.scripting.sightly.SightlyException: Compilation errors in org/apache/sling/scripting/sightly/libs/fd/franklin/components/form/v1/form/form__002e__html.java:_Line 40, column 1814 : com.adobe.cq.

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 access settings of the AEM Code Sync App be just enough?

I have created form using Document based approach that is using Google docs and Excel sheet Added specific rules to some fields and some conditions also working fineLinked with Adobe Sync app and previewed and published Now while submitting its showing error and submit option not working as expected 

Hello,I’m looking to streamline the process of managing content change requests for our website, which is hosted on Adobe Experience Manager (AEM) Sites. Currently, employees at our company send requests (e.g., changes to copy or images) via email to the author of the page, which can be inefficient and difficult to track.I’m considering using AEM Forms to create a centralized request system where employees can submit change requests through a form hosted on our internal intranet. I would like this form to integrate seamlessly with AEM Sites and trigger workflows to route requests to the appropriate content authors for review and implementation. Employees do not have access to AEM, so the solution needs to work externally (via intranet) but manage tasks and submissions internally within AEM.I'd appreciate some guidance on this matter and knowing if this is the right way to go or if Adobe offers a different solution to solve this problem.Thanks.

Hey guys, I am trying to use this custom video block from aem assets plugin.https://github.com/adobe-rnd/aem-assets-plugin/tree/main/blocks/videoThe preview for these blocks are here: https://main--assets-blocks--hlxsites.aem.live/video-block-demoHowever, when trying to run them on my local EDS project, I am not seeing the same functionality. This is most likely due to the fact that I don't have AEM Assets and Dynamic Media OpenAPI. Now, I need to build custom video heroes, with custom icons and overlay text blocks, with Youtube hosted videos. Currently I am using the standard Video block, but are there any other solutions or blocks I can use without any additional licenses? Thanks

How do I delete these sitemap.xml pages from the xml?<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:xhtml="http://www.w3.org/1999/xhtml"><url><loc>https://apple.com/</loc><lastmod>2024-12-17</lastmod></url><url><loc>https://apple.com/contact-us</loc><lastmod>2024-12-05</lastmod></url><url><loc>https://apple/tools/sidekick/blocks/image</loc><lastmod>2024-12-18</lastmod></url><url><loc>https://apple/tools/sidekick/blocks/text</loc><lastmod>2024-12-18</lastmod></url><url><loc>https://apple/tools/sidekick/blocks/banner</loc><lastmod>2024-12-18</lastmod></url><url><loc>https://apple/tools/sidekick/blocks/iframe</loc><lastmod>2024-12-18</lastmod></url></urlset>

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 what would protect https://<branch>--<repo>--<owner>.aem.live, do we even need to protect https://<branch>--<repo>--<owner>.aem.live?

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 our AEM Edge Delivery Service website, we wish to present a form to them. Once the form is submitted, we want post the data to a custom CRM like Sales Force. In order for us to connect to the CRM, we need some backend implementation which will connect to the CRM via Oauth2. What is the best way to archive this? 

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.dev/content/core-components-examples/library/core-structure/language-navigation/language-structure/us/en/language-navigation.html  

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