Experience Workspace

Experience Workspace is a modern CMS workspace where humans and agents collaborate to build, edit, and optimize experiences​.

Introduction

Experience Workspace reflects and supports how content creators generate content in the agentic age. Through ideation and delivery, it brings together the tools creators need to publish their content.

• Visual editor
• AI assistant
• Optimization opportunities
• Enterprise context
• MCP / Agents / Skills support

Experience Workspace is a collaborative platform that offers the capabilities you need to react in an agentic environment.

• Authoring - Create your content with intuitive tools

  • Visual editor offering a WYSIWYG canvas
  • AI assistant for quick access to prompts and skills
  • Multi-user and agent support for human/AI collaboration
  • Assets integration for quick access to AEM Assets for all of your media

• Intelligence - Optimize your content with a system that knows your content

  • Enterprise context provides brand identity, marketing signals, and other data
  • Author memory learns and builds skills for velocity
  • MCP / Agents / Skills can connect any Adobe or 3rd party app
  • Optimization opportunities are generated from insights into your sites and external signals

• Operations - Publish and manage your content

  • CMS capabilities allow you to manage, publish, and schedule your content and generate workflows
  • CMS skills management to extend the CMS
  • MCP support for integration in LLMs
  • REST API for API-first access

Setup

Setting up Experience Workspace consists of a) adding quick edit to your codebase, and b) configuring the DA editor to use the Experience Workspace editor instead of the default DA editor.

Quick Edit

To enable WYSIWYG capabilities, Experience Workspace relies on quick edit. To set up quick edit for your project, please follow the steps in the quick-edit setup guide.

Editor Setup

In DA, open your org configuration by navigating to https://da.live/config#/<your-org-name>/.

Insert the following key/value configuration:

You can optionally only enable Experience Workspace for a subsection of your site by adding a path like /<org>/<site>/<path> in the value column. You can have as many editor.path configurations for different sites and subpaths as you like.