Queries - EDS for Existing AEMaaCS Projects

[Som_Adobe]

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 -

1. 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.
2. 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 using Universal Editor ? On Update using UE the content needs to get updated back on File system ?
3. Is there a chance of Dirty Read/Write of Documents when concurrent authors are operating simultaneously on the same document ?
4. Can there be multiple mountpoints mapped to a single EDS application based on page path ? Like /content/abc - mount from AEM Author, I need to save all changes back on JCR for anything update under this path, /content/xyz - mount content from File Drive, I need all changes to reflect on Google / Word Doc ?

[Martin_Buergi_Adobe · Accepted solution]

Hi,

Thank you for your questions.

1. You cannot use Edge Delivery blocks & sections outside of Edge Delivery pages. You need to move the whole page on Edge Delivery. There is not need to move your whole site, you can start moving just a few pages and delivery then in a side-by-side fashion using CDN rules.

2. As of today, you cannot use Universal Editor on top of Sharepoint or Google documents. We have not seen (yet) real demand of authors to do both on the same page. It will add authoring complexity we want to avoid with doc-based authoring. However, if authors want to switch at one point, we have tools to help moving the content from doc-based to AEM or the other way around.

3. For Sharepoint / Gdrive documents, this would be handled by the respective solution. For Universal Editor, collaborative editing it is on the roadmap for 2025.

4. Yes, that is possible, but keep the authoring experience in mind if you need to cross-reference between content sources.