Adobe Experience Manager Edge Delivery Services

Planning your next AEM EDS implementation? AEM Sites or Edge Delivery Services (EDS)?Explore the complete differences in architecture, content authoring, deployment pipelines, performance, developer experience, and migration considerations to choose the right solution for your digital experience platform.  Click here to Read More

In Universal Editor, when trying to align text in Rich Text field by using default alignment option (left, center, right), it only adds inline style. Upon saving changes and exiting out of RTE, all inline styles are removed.I want to have per-paragraph alignment option within a rich text field so didn’t do this through custom model field. Any fix for this? Like adding a class instead of inline styling so this can actually work?

Are you exploring Adobe Edge Delivery Services (EDS) for your next AEM project?Want to understand:• What EDS actually is• Why Adobe moved from Helix → Franklin → EDS• How EDS differs from traditional AEM Sites• Why Lighthouse performance scores matter• How the edge architecture works in real-world projects  Click here to read the complete guide:https://www.aemcq5tutorials.com/tutorials/what-is-adobe-edge-delivery-services-eds/

I see a OOTB response header for EDS pages - Vary: Accept-Encoding,X-Forwarded-Host, is there a way to edit the values present in this header?

Can we have add-on Adobe Workfront plugin/extension for AEM Universal Editor UI to show Adobe Workfront task/assignment context directly inside the AEM Universal Editor UI so authors can see:assigned tasks approval status due dates project metadata workflow state

 Hi Team ,We are trying to enable the “Open in new tab / Same tab” option in the Universal Editor RTE hyperlink dialog for the EDS Franklin text component (core/franklin/components/text/v1/text). We added the following configuration based on Adobe documentation:"rte": { "plugins": { "link": { "features": { "target": true } } }, "actions": { "link": { "hideTarget": false } } }However, the hyperlink dialog still only shows:Text Path or URL Titleand the target selection option is not displayed. Could you please confirm whether link target selection is currently supported for the Franklin text component in Universal Editor, or if any additional configuration/customization is required?Thanks.https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developing/universal-editor/configure-rte

Hi everyone,I am currently working on an EDS Xwalk project. According to the following Adobe documentation: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developing/universal-editor/field-types#rich-text https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developing/universal-editor/configure-rte The RTE should support features such as indentation and image insertion. However, in our actual Xwalk project, these options do not appear in the toolbar.Our users need to use tables and images within the rich text field. Does the Xwalk project currently lack support for these features?Additionally, is there any detailed documentation, component definitions, or specifications specifically for Xwalk? Most of the resources we found so far seem to focus primarily on DA (Document Authoring). [Official Documentation Screenshot][Actual UI Screenshot] 

Hi everyone,We are currently working with Edge Delivery Services using AEM Authoring as the content source (spreadsheet-based publishing flow).We noticed that after publishing a spreadsheet and generating the corresponding JSON, French accented characters are being replaced by the Unicode replacement character (�).Example:Aller simple � partir deinstead ofAller simple à partir deWhat we validated so far:Spreadsheet content inside AEM Authoring looks correct Source content is UTF-8 encoded Frontend rendering path is correct Generated JSON already contains the replacement characterThis makes us think the issue may happen somewhere in the spreadsheet → JSON publishing pipeline, possibly related to charset handling during transformation.Has anyone experienced something similar when using EDS with AEM Authoring and spreadsheet-based content?Are there any known encoding considerations, charset configurations, or best practices we should review?Thanks in advance!

Hello,we are trying to add seo schema to our page, Adobe's documentation suggests to use json-ld to author seo schema, but I am clueless on how to add it as a property to page.json. Whenever I tried to add it as a property to page.json, the content which I author in that page is being rendered as a meta tag with name property which I have defined in page.json. It is not rendering as script tag as it was mentioned in documention. Could anyone help me with this.  Thank You.

How to set up the storefront for Adobe commerce as a cloud service?

EDS edge workers can be suitable for API authentication. Please provide your comments

Hi everyone,I’m working with AEM + Universal Editor + Edge Delivery Services.Is there a way to display a custom name per block instance in the Content Tree, based on a model field (e.g., authorLabel)?I want authors to label blocks like “Hero – Home” or “Hero – Campaign” and see that in the tree, instead of just the default component name.Is this supported or is there any extension point to achieve it?Thanks!

Hello,I'm currently working on a project using X-walk and the Universal Editor and have a question regarding how sheets are handled.Does the Experience Delivery Service (EDS) support only one sheet per type (e.g., taxonomy, metadata) for an entire project? When I try to create mappings for a second sheet of a specific type (for example, a second metadata sheet named metadata2 or a second taxonomy sheet), publishing it to the EDS fails to generate a json file, resulting in a 404 error.I’ve also read in the documentation that using a shared- prefix might be a solution, but this approach does not seem to work with X-walk either. If X-walk projects are indeed limited to a single sheet per type, is there another recommended approach to implement page-specific sheets within the EDS? Thanks in advance for any insights you can provide!

I am currently working on the Universal Editor and xwalk projects.Based on the official documentation at https://experienceleague.adobe.com/en/docs/experience-manager-edge-delivery/using/build/indexing and https://www.aem.live/docs/indexing-reference, I expected to retrieve the showbreadcrumb metadata from the pages by adjusting the helix-query.yaml file.version: 1indices: pages: include: - '/**' exclude: - '/**.json' target: /query-index.json properties: lastModified: select: none value: parseTimestamp(headers["last-modified"], "ddd, DD MMM YYYY hh:mm:ss GMT") robots: select: head > meta[name="robots"] value: attribute(el, "content") title: select: head > title value: textContent(el) showbreadcrumb: select: head > meta[name="showbreadcrumb"] value: attribute(el, "content")However, the returned results still only contain the lastModified, robots, and path fields from before the m

Hi,When trying to create an Edge Delivery Services site via https://da.live/start, I get this error after entering my AEM GitHub repo URL:“You are not authorized to create this site in the corresponding DA organization.”I’m logged in with an Adobe ID that has AEM Author access, and I have access to the GitHub repository.Steps FollowedOpened https://da.live/start Entered my AEM codebase GitHub repository URL (example: https://github.com/<org>/<repo>) Clicked GoEnvironment DetailsAEM as a Cloud Service Edge Delivery Services Universal Editor enabled Logged in with my Adobe ID (has AEM Author access) GitHub repository is accessible to meWhat I’ve Already CheckedGitHub repo access ✅ Logged into the correct Adobe account ✅ Edge Delivery is enabled for the program ✅Questions:What permissions or roles are required to create a site via da.live/start? Does the user need to be explicitly added to a DA / Edge Delivery organization in Adobe Admin Console? Is this controlled by IMS org,

Environment:AEM as a Cloud Service using Edge Delivery Services (EDS). Authoring through the Universal Editor (UE) and standard AEM Sites console. Translation Provider: Out-of-the-box (OOTB) Microsoft Translator.Requirement: We need an automated "zero-click" translation process.Source Language: English (/content/gmr/en) Target Languages: Multiple (tr, fr, es, ja, etc.)When an author modifies English content, it should automatically trigger a translation to all target languages and update the language copies for EDS delivery.Current Issues:Missing Rollout Option: The standard "Push to Translation" rollout configuration is not available in our AEM Cloud instance. Launcher Failures: We have configured a Workflow Launcher on Node Modified to trigger the WCM: Translate Language Copy workflow. The workflow instance starts but remains in the "RUNNING" state indefinitely. The setup works perfectly when triggered manually via the "References" panel, but the automated version hangs. MSM Integr

I have a section of my site on EDS while the majority of it is on AEMAACS. My question was on how to include launch script to my EDS pages, since they are environment specific?

Go to https://da.live/, navigate to your site, update the organization permissions, and then publish the page from the console.

We can share the ideas, suggestions, bottle necks , do and don’ts, any known issues on projects with Eds + universal editor. We can meet in person and talk more about this share the knowledge.

Hi , I am currently learning EDS and wanted to get hands on repoless. Iread that it needs admin key and api access to configure the repoless.Is there any way that we can do some hands-on on our own without using organisational keys?

Three quick questions for AEM teams. Answer whichever applies to you: 𝐐𝐮𝐞𝐬𝐭𝐢𝐨𝐧 𝟏: AEM Cloud MigrationIf you had to migrate to Cloud Service tomorrow, how ready would you be?🟢 Ready — fully assessed🟡 Mostly ready — some unknowns🟠 Haven't fully assessed🔴 Not ready — significant technical debt 𝐐𝐮𝐞𝐬𝐭𝐢𝐨𝐧 𝟐: Edge Delivery ServicesWhat's your EDS strategy?📋 Already using EDS or Adobe's new Modernization Agent🔍 Evaluating it❓ Haven't started thinking about it🤷 Not sure what EDS is (no judgment — it's new) 𝐐𝐮𝐞𝐬𝐭𝐢𝐨𝐧 𝟑: AccessibilityHow confident are you in your AEM site's WCAG/EAA compliance?✅ Fully compliant and tested🔶 Mostly compliant with known gaps⚠️ Haven't done a proper audit🚫 Not on our radar yet Drop your answers in the comments. I'm genuinely curious where the community stands. I'll share the results with my analysis next week. (And yes, I've worked with teams in all four categories on all three questions. No judgment here.) #AEM #AdobeExperienceMana

Edge Delivery Services has changed the game for Lighthouse scores, but the authoring experience is now the big conversation. I’m looking to gather some real-world perspectives on the best 'flavor' of authoring for AEM Edge Delivery Services (EDS).​i see we have three distinct paths and I'd love to hear from anyone who has moved between them:​Pure Document Authoring (Google Drive/SharePoint): The speed is unmatched, but how are you handling complex governance at scale?​DA.live (Document Authoring): Is this the 'Goldilocks' zone for asset integration, or does it add an unnecessary layer?​Universal Editor with AEM Sites: For those who need MSM and heavy localization, does the performance of EDS still feel 'magical' when coming from a full AEM Cloud Service backend?​Which combination have you found offers the best balance of author velocity and developer sanity? Looking forward to your insights!" 

We are running an EDS implementation using document-based authoring via da.live with Fastly CDN. Our blog section uses three custom blocks:blog-grid — paginated card listing with category filtering, tag colour mapping, and authorDate sorting page-list — sidebar block surfacing the most recent posts for the current category cards — category navigation iconsContent is authored in da.live and published through the standard EDS content bus. The query index URL is resolved dynamically at runtime via /config.json using getConfigValue('query-index').The Problem:All three blocks render entirely client-side via JavaScript. On the initial HTTP response, the page shell delivered to crawlers looks like this:html<div class="blog-grid"> <div><div>Pagination-limit</div><div>10</div></div> <div><div>Title</div><div>Category Name</div></div> <div><div>Guides</div><div>bg-guides</div></div&g

We are using Universal Editor with Edge Delivery Service, I would like to know how to customise the OOTB text styles available in Text Default content type. For this particular example I would like to add more options to add alignments.  It's not possible to apply any customisations inside RTE fields through the json model.Could you advise on the problem?

Hi everyone,I’m currently working on setting up an Edge Delivery Services (EDS) site using an Adobe repository and would appreciate some guidance.My goal is to: Set up a new EDS project using the official Adobe repository Configure the required integrations to create and load the website using AEM Sites authoring Create pipelines, deploy the site, and preview content I’ve gone through the documentation, but most of the references are based on using a public GitHub repository. In my case, I’m working with a private repository (Adobe repo).At the moment, I’m facing an issue with site ownership verification. Even after adding the required verification file, the verification is not successful. Currently, my repository only contains this verification file and does not yet include files like fstab.yaml or other standard EDS configuration files.It would be really helpful to understand the correct approach for private repository setups, EDS site creation, especially around ownership verifi