--- title: Content Authoring in Adobe Edge Delivery Services description: Explore Adobe Edge Delivery Services authoring models, from Universal Editor to Google Docs, and boost performance, flexibility, and speed to market. publish date: 2026-04-23 author: Daniela Romero image: https://media2.oshyn.com/-/media/Oshyn/Insights/Blog/2026-04-23-Content-Authoring-in-Adobe-Edge-Delivery-Services/blog_hero_eds-in-context-vs-document-based-authoring.jpg?rev=d46f0fca0a924df1a6275760d839aa90 url: http://www.oshyn.com/blog/2026/04/eds-in-context-vs-document-based-authoring --- # Content Authoring in Adobe Edge Delivery Services ![Hands building legos](https://media2.oshyn.com/-/media/Oshyn/Insights/Blog/2026-04-23-Content-Authoring-in-Adobe-Edge-Delivery-Services/blog_hero_eds-in-context-vs-document-based-authoring.jpg?rev=d46f0fca0a924df1a6275760d839aa90&hash=D5ACFAC515B98B9F186AF7028B42B982) Modern websites require fast performance, flexible authoring, and rapid development cycles. Yet many enterprises struggle with content bottlenecks caused by overly technical CMS authoring experiences. Adobe Edge Delivery Services (EDS), part of Adobe Experience Manager, introduces a new architecture that delivers content quickly through edge infrastructure while simplifying development and content-creation workflows. One of the most distinctive features of EDS is its flexible content authoring model. Content can be created using various tools, depending on the team's needs, including the Universal Editor, Document Authoring, Google Docs, and Microsoft SharePoint. This also gives them the flexibility to improve operational efficiency, speed to market, and employee productivity. In this article, we’ll explain how content authoring works in EDS and the benefits it can provide. ## Key Takeaways - Adobe Edge Delivery Services supports multiple content authoring models, including the Universal Editor for in-context editing and document-based editing via Document Authoring, Google Docs, and Microsoft SharePoint. - Teams already working within AEM might favor the Universal Editor, which provides WYSIWYG editing and a component-based architecture. Meanwhile, document-based authoring can suit non-technical teams who prefer familiar office tools with minimal developer involvement. - Choosing the right authoring model depends on team composition, existing tooling, governance requirements, and the complexity of the site being built. - Organizations evaluating or implementing Adobe Edge Delivery Services can work with Oshyn to navigate architecture decisions, development, and post-launch enhancements across the full AEM lifecycle. ## What is Edge Delivery Services? Adobe Edge Delivery Services (EDS) is a modern web delivery architecture designed to improve website performance and simplify development workflows. Instead of relying on traditional server-side rendering pipelines, EDS delivers pre-processed content directly from edge locations using a CDN-first architecture. In EDS, developers build reusable front-end components called blocks. These blocks define how content is structured and rendered on the page, enabling teams to create modular, reusable layouts.  ## How Blocks Work in EDS? Blocks are the building units of pages in Edge Delivery Services. They are reusable components implemented with HTML, CSS, and JavaScript that transform structured document content into interactive web elements. Blocks are typically stored inside the blocks directory of the repository. Each block lives inside its own folder, and the folder name usually matches the block name. ![Typical repository structure](https://media2.oshyn.com/-/media/Oshyn/Insights/Blog/2026-04-23-Content-Authoring-in-Adobe-Edge-Delivery-Services/eds-in-context-vs-document-based-authoring_1.png?rev=1a8df1ed652447ad99b1213c053cc0f1?) *Typical repository structure* When a document is processed by Edge Delivery Services, its structured content is converted to HTML and enhanced with blocks that apply styling and functionality defined in the repository. ## Content Authoring in Edge Delivery Services Unlike traditional CMS platforms that rely on a single content editor, Edge Delivery Services allows authors to create content using multiple tools. Teams can choose the authoring environment that best fits their workflow, whether in-context editing or document-based editing. **In-Context Editing** In-context editing lets authors modify content directly on the page using the Universal Editor, offering a visual editing experience similar to traditional CMS interfaces. This approach may feel familiar to teams already working with Adobe Experience Manager, as the Universal Editor is integrated into the AEM environment. **Document-based Editing** Document-based editing allows authors to create structured content using tools such as Document Authoring, Google Docs, or Microsoft Word. In these workflows, the content is stored in a document repository rather than directly in AEM. Edge Delivery Services connects to these content sources using a configuration file called fstab.yaml. This file defines mount points that allow EDS to retrieve content from different repositories and transform it into web pages. For example, when using Google Docs or SharePoint, the mount points connect the EDS project to the corresponding document repositories. In projects using the Universal Editor, fstab.yaml is also used to connect the Edge Delivery Services project to the AEM content repository. The following sections describe the most common authoring tools used with Edge Delivery Services and how they support different authoring workflows. ### The Universal Editor The Universal Editor provides a visual, in-context editing experience that allows authors to modify content directly on the page they are viewing. This approach is similar to traditional CMS editing interfaces, where authors interact with components and content in real time. This makes it easier for authors to understand how content will appear to end users. The Universal Editor works across different architectures, including both headless and headful implementations. It also integrates with Adobe Experience Manager capabilities and can be used alongside Edge Delivery Services to maintain high-performance content delivery. Some benefits of using the Universal Editor include: - Increased author efficiency through in-context editing. - Support for advanced AEM capabilities such as MSM, localization, and workflows. - A familiar visual editing experience similar to a traditional AEM author experience. ![In-context workflow](https://media2.oshyn.com/-/media/Oshyn/Insights/Blog/2026-04-23-Content-Authoring-in-Adobe-Edge-Delivery-Services/eds-in-context-vs-document-based-authoring_2.png?rev=591b9a810e9a4572b6687ebfe992e1ef?) *In-context workflow* If you want to try out the Universal Editor, Adobe has a tutorial you can follow. ### Document Authoring Document Authoring is a document-based editor designed specifically for Edge Delivery Services. It allows authors to create and edit content directly within a structured document interface while previewing the resulting page. The editing experience is similar to common word processors such as Microsoft Word or Google Docs. Some advantages of using Document Authoring include: - The setup is simpler than in Google Docs or SharePoint. - No external integrations are required for it to function. - Extensibility is implemented through blocks built with HTML, CSS, and JavaScript, allowing developers to extend functionality using standard web technologies.⠀ Adobe also has an AEM Document Authoring tutorial. ### Google Docs / SharePoint Authoring EDS supports document-based authoring using Google Docs or Microsoft SharePoint. In this model, authors create content directly in Google Docs or Microsoft Word, while the documents are stored in their respective repositories. These repositories are connected to the EDS project, which retrieves and transforms the documents into web pages. Some benefits of using this approach include: - A familiar editing experience for teams already working with Google Docs or Microsoft 365.  - An intuitive workflow for marketing and content teams.  - Integration with existing Google Workspace or Microsoft ecosystems.  - Benefits of using familiar office tools, such as permissions management, copy-and-paste editing, and built-in collaboration features. If you want to integrate SharePoint or Google Drive as your content repository, review the AEM content repository tutorial. ![Document-based workflow](https://media2.oshyn.com/-/media/Oshyn/Insights/Blog/2026-04-23-Content-Authoring-in-Adobe-Edge-Delivery-Services/eds-in-context-vs-document-based-authoring_3.jpg?rev=e86c510e7d2e4a69b7778ebc9b0815ca?) *Document-based workflow* ## Comparison of Edge Delivery Services Authoring Models | Feature | In-context | Document-based | | --- | --- | --- | | Authoring Tool | Universal Editor | Document Authoring, Google Docs, SharePoint | | Target Users | Content author and marketing teams working within AEM | Non-technical users familiar with office tools | | Publishing workflow | Publishing is controlled through AEM workflows and publishing tools | Document changes are converted to web content and published automatically | | Editing Experience | WYSIWYG in-context editing in a web interface | Edit content like a normal document | | Content structure | Uses components and structured content models | Uses structured sections and tables within documents to define layout | | Content storage | Stored in the AEM repository as structured content | Stored as documents in Google Drive or SharePoint | | Learning curve | Higher — requires understanding of AEM UI and components | Very low — most users already know Word or Google Docs | | Governance & enterprise features | Full CMS capabilities, including workflows and permissions | Limited built-in governance | | Content model flexibility | High — component-based architecture with configurable models | Limited — document structure defines layout | | Technical complexity | Medium to high, depending on implementation | Low | | Developer involvement | Developers often need to build components and models | Minimal for content updates | | Extensibility | Extended through AEM components and content models | Extended through blocks built with HTML, CSS, and JavaScript | As shown in the table above, the Universal Editor may be easier for authors who are already familiar with Adobe Experience Manager capabilities, as it provides full CMS features, including component-based authoring, governance, and integration with AEM Assets. In contrast, document-based authoring with tools like Google Docs or Microsoft SharePoint can be appealing to teams that prefer collaboration and familiar editing environments, enabling non-technical users to create and update web content using tools they already know. ## Wrapping Up Edge Delivery Services provides a flexible content authoring ecosystem that supports multiple authoring methods. Whether teams prefer document-based authoring through Document Authoring, Google Docs, or SharePoint, or visual in-context editing with the Universal Editor, EDS allows developers and content authors to collaborate efficiently while maintaining high-performance content delivery. By supporting multiple authoring approaches, EDS enables organizations to balance developer productivity, content authoring flexibility, and performance. Choosing the right authoring model ultimately depends on the team's needs, the existing collaboration tools, and the complexity of the website being built. If you're evaluating Adobe Edge Delivery Services or planning an AEM implementation, Oshyn is available to help. Our Adobe expertise covers the full lifecycle, from architecture decisions and development through post-launch enhancements and maintenance. Reach out to see how we can support your digital experience needs.