Choosing the right authoring model can make or break your Edge Delivery Services project, and most teams don't realize they're locked into a decision until it's too late.

Document Authoring, Universal Editor, and DA.live each hand your content team a different editing experience, and each one shapes your block architecture, your localization workflow, and your content velocity. Pick wrong, and you're refactoring and rearchitecting which can lead to lost time for you and your team. But if you pick right, authors, developers, and architects all get to work the way they want to.

Join us on September 30th for a working session built for anyone who's had to make this call, or needs to support making this decision in the near future. We'll level-set on where Document Authoring, Universal Editor, and DA.live each sit in the EDS landscape, then dig into the real decision framework: who's authoring, how structured the content needs to be, content velocity, and governance behind it all.

From there, we'll get a hands-on demonstration by Gary Fuller with Universal Editor for headless implementations, where he'll show a WYSIWYG experience that proved alignment of the content model and the app structure.

We'll close by looking downstream, and how each model affects block development, preview/publish behavior, and localization. We'll also look at what happens when your content outgrows the model you started with.

Whether you're an author choosing a tool, a developer building the blocks behind it, or an architect setting the pattern for your organization, you'll walk away with a clear understanding on what drives this decision.