FAQ

Can I use DA in production?

Yes. DA is an Edge Delivery Services document-based content provider just like SharePoint and Google Drive. It is considered an Adobe early-access technology preview but you are encouraged to use it in production if it fits your needs.

Note: if you choose to use DA in production context:

1. AEM Edge Delivery Services still provides 99.99% uptime for the delivery of your site.
2. Please reach out on Slack, Discord, or Teams to ensure you are supported through the lifecycle of your project.

Who is working on and supporting this?

Several teams across Adobe working in collaboration with Adobe partners. You can see the full list:

https://github.com/adobe/da-live/graphs/contributors

https://github.com/adobe/da-admin/graphs/contributors

Do I have to do another migration if I'm already on Google Drive or SharePoint?

It's a bit nuanced, but the short answer is no. DA stores content in the same format as AEM Edge Delivery Services. This has the following implications:

1. There's no transformation of content that needs to be done.
2. No changes to your project codebase need to be done.
3. If you decided DA does not fit your project, your content can be moved back to SharePoint or Google Drive easily.

Where is DA content stored?

DA content is stored within the same infrastructure as AEM Edge Delivery Services. It is stored free from other cloud providers like SharePoint, OneDrive, Google Drive, Dropbox, etc.

Does this mean SharePoint or Google Drive go away?

Probably not.

First, both systems are almost always used when making content that funnels into your web content management system (WCMS).

Also, depending on the persona, the familiarity of SharePoint or Google Drive may still be the preferred authoring tool. If you have multiple projects, you may find SharePoint or Google Drive is a better fit for some authors.

What is your roadmap?

The current roadmap is based on blocking issues for VIP customers and items that improve operational efficiency. If you're still reading this, here's a few of the current (as of this writing) items:

1. Fine-grained authorization
2. Self-service disaster recovery
3. Sheet collaboration
4. Broaden localization use-cases
   1. Config-less hardening
   2. Connector API documentation
   3. DNT Query Language (DNTQL)
5. Browse improvements
   1. Sort by date
   2. Select all
   3. Move
   4. Preview & publish
   5. Copy URLs
6. Search & replace improvements
   1. Recipe - search by block name
   2. Recipe - search by metadata key
7. General editor improvements (see GH issues)
8. Library improvements
   1. Support new page plugins
   2. Move to AEM library schema
   3. Support full-screen modal
   4. Move AEM Asset button into library
   5. Make AEM Tags first-class citizen (currently SDK plugin on bacom-sandbox)

What are the licensing costs?

At the time of writing, DA is available to all Edge Delivery customers as an early-access technology preview.

Does this mean AEM authoring tools (Touch UI, Universal Editor, etc.) go away?

No.

We believe there's a lot of different use cases to cover, and DA is only one path. DA is not meant to be an SPA editor or an in-context (wysiwyg) editor. It's un-apologetically a document-based editor meant to be compatible with CMD + A, CMD + C, CMD + V workflows from Word or Google Docs.

What started this?

While many projects can benefit from the approachability of known content management systems, other projects can benefit from the tools and technologies provided by the Adobe Experience Cloud ecosystem. DA was built to provide a familiar document authoring interface and pair it with content management APIs backed by Adobe services.