Queries Reagrding Edge Delivery Services

[Som_Adobe]

Context

I 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 ? 

• How do we do fresh authoring of web pages, or how do we drag-drop new components on an existing page using Universal Editor? UE does not recognize "parsys" but treats content in sections/blocks. So I do not see a parsys on Universal Editor. Also the URL provided to it is from "View as Published" mode with ?wcmmode=disabled. So how do I create and author a fresh page based ona pre-defined editable template from scratch using Universal Editor ? I do not see any Adobe dcoumentation on the same as yet.

• Document-Based authoring does not store any content on AEM JCR by OOB behaviour. Therefore, Sling Content Exporters won't be able to deliver the content as a service. So how do we export that relevant content to external channels such as a Mobile App with customized attributes as JSON may be, which the App already understands today ?

• Document Sharing requires the drive to be shared with helix@adobe.com for AEM EDS to avail the document content and preview/publish using AEM Sidekick Browser Extension. Is there a security issue in sharing all client confidential documents with the AEM user ? Is there a work around to avoid sharing file system documents with the Helix AEM user ?

• EDS document-based approach uses AEM Code Sync and creates web pages on EDS Helix preview server. It can then be published to Live server. These domains and URLs are different - Preview: https://{branch}-{repo}--{owner}.aem.page   (Max 63 Characters) and Live: https://{branch}--{repo}--{owner}.aem.live (Max 63 Characters). How do these unify with the domain and URL of the client website ? Is there a need of a reverse proxy to map these domains internally ?

• How wise will it be to suggest EDS and UE for clients using AEM 6.5 On-Prem or AEM 6.5 AMS, standing today ?

Thank You everyone in advance for all your help !

[ShaileshBassi]

Hi @Som_Adobe 

Please find below answer to your queries:

1. If the EDS Delivery Configurations are created & then the site is created using the site template, it will automatically open the AEM based authoring in the Universal Editor. 

Point to Note - While developing with a local AEM SDK, Adobe’s Universal Editor Service can not be accessed from the internet. Reference https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/dev...

2. There is the file named "component-filters.json", which defines which particular components will be part of which section.

[{
    "id": "main",
    "components": [
      "section"
    ]
  },
  {
    "id": "section",
    "components": [
      "text",
      "image",
      "button",
      "title"
    ]
  }
]

Reference - https://github.com/adobe-rnd/aem-boilerplate-xwalk/blob/main/component-filters.json

3. There is no OOTB exporter available for exporting the content created for AEM based authoring directly like we have in AEM Sites. Only solution over here would be writting your own wrappers via servlets or anything else.

4. I would recommend opening the Adobe Support Ticket for the same and check for the security.

5. For the domain, you can either use Adobe Managed Fastly CDN or your own CDN and add the respective traffic rule.

Hope this helps!

Thanks