The EDS Dilemma : Battle of choice Document-based vs DA.Live vs AEM Cloud with Universal Editor

​@Shashi_Mulugu This is a great discussion, thanks for raising it! 

From my experience, each approach really has trade-offs depending on scale, localization needs, and governance complexity. Adobe guidance clarifies the authoring options for AEM EDS:

• Universal Editor: Recommended for most teams that supports full AEM capabilities like MSM, localization, workflows, and integrates seamlessly with EDS for high-performance delivery. | Documentation

• Document-Based Authoring: Best for simpler content and quick turnaround, especially if your authors are already using these tools. Documentation

• Document Authoring: A document-centric editor built for EDS. Ideal for teams wanting a lightweight, document-first workflow, but it doesn’t replace the Universal Editor for full AEM workflows. Documentation

I’d love to hear from you and others, for teams managing multi-market or multi-language setups, which approach have you found balances author speed and maintainability best?

Choice of EDS flavor I believe is actually quite straightforward.

If looking at Document Based (Word/Google) versus Document Authoring (DA.live a.k.a. Adobe) the choice IMO is very clear - go with the latter.  DA gives Adobe full control of both the Authoring UI and content storage, which is critical to Adobe providing the best authoring experience and platform capability.  MS Word and Google are never going to be all that interested in modifying their UI or APIs to better serve EDS, whereas DA will consistently progress with new features and QoL improvements. We’re already seeing some of these features in DA, such as support for MSM/i18n operations, bulk content updates, author select boxes, authoring library plugins, etc.

My beliefs on UE are that it will apply in some edge cases, but you should only choose UE if you’re 100% certain of specific needs that only it can achieve.  UE feels a bit of a heavily engineered solution for something that squarely hits a middle ground between AEM and UE. Because it’s not fully classic AEM, it doesn’t benefit from all the capabilities of traditional AEM, and because it’s not fully EDS it adds complexity and weight to a project with little limited benefits. I think you will see a majority of projects either go classic AEM or fully EDS (DA), and UE will fill a marginal middle space of 5-10% of new projects similar to how the SPA Editor (now deprecated) in AEM did in the past.

Hi ​@Shashi_Mulugu this is a really interesting subject and one that my business is experiencing in real time. We recently migrated from Sitecore to Adobe and went initially to Document-based authoring using Microsoft Word/Excel. However, we’re now moving again to DA for a variety of reasons one of which is governance, but also for the features that are important to us like live preview, referential DAM integration, and also channel management (which we’re still working but seems like it’s going to be easier with DA). In a world where we want to democratise content tasks across the business while still retaining a “core” team of content authors for more complex content operations, we think DA will give us the best balance.

it would be awesome to hear from the experiences of other customer’s though - particularly those that are attempting to tackle the issue of lot of stakeholders/authors/business users and how governance within DA is managed.

If you are certain that you will be using EDS, the ideal solution would be to use Document Authoring (DA), as it supports both document-based authoring and WYSIWYG (Universal Editor) authoring.

However, DA is currently a community-supported product, and Adobe does not provide SLA-backed support for it.

More details about DA authoring using AuthorBus at https://adapt.to/2025/schedule/unlocking-edge-delivery-authoring-with-authorbus

​@Shashi_Mulugu Before the DA launch, if you had to take a decision, I could have suggested going with the universal editor because that offers the same authoring experience as what authors have been familiar with over the past so many years. Now DA is kind of a somewhat mixed bag of both UE and Doc based so it's now becoming a favorite and it almost solves all the issues and challenges faced in the doc-based approach. 

However, the development efforts remain the same, if you choose any of the approaches, it is just a matter of authoring the experience you have to give to the business.