DA - Introduction #2784
auniverseaway
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
As many know, there has been a small team of volunteers across AEM engineering, adobe.com engineering, and Adobe partners building a 100% E2E alternative to SharePoint. This project is called DA. Short for Document Authoring.
DA is the answer to the question, "Why doesn't Adobe make a document editor?"
DA has five major pillars
DA is un-apologetically a document-based editor. There are many great AEM-based solutions for other types of web content management; headless, universal editor, etc.
Today
As of today, DA is very much not an AEM product. Similar to Helix in the early years, DA is an advanced research project. Also like Helix, if an Adobe customer is aware of this research and wants to use it, they can, and we (the DA team) will support them. This is happening today and an external Adobe customer will be going live with DA next month.
For adobe.com, DA has been approved and used for sandbox and non-production use cases only. DA's import speed lends itself to creating a lot of content quickly without the burdens of the DOCX format or the rate limiting issues of SharePoint. We have seen our SEO team be successful in testing mass content changes that are not reasonably possible in SharePoint.
Tomorrow
We have identified a site on adobe.com for a production pilot of DA. We'll be working with engineering and product leadership to ensure they're happy and see the same value in DA that we do today. As always, I'll share more details as they solidify. We are also in talks with other external customers who see DA as a path to simplified and scalable web content management. All this being said, we have to be careful that we do not on-board too many projects.
Links
For you
If you have any questions, please don't hesitate to ask!
Beta Was this translation helpful? Give feedback.
All reactions