Workspaces is no longer only about staging content. It is becoming part of how Drupal can handle governed change across content, config, and AI-assisted workflows.

Prerequisite

Participants will get the most value from this session if they already have some familiarity with:
* Drupal core concepts such as entities, configuration, and editorial workflows
* Content Moderation and basic publishing workflows in Drupal
* General awareness of AI tooling in Drupal, even if they are not using it yet

Target Audience

This session is aimed at Drupal developers, technical leads, solution architects, and experienced site builders who are working on enterprise Drupal platforms with complex publishing needs or who are already using, evaluating, or extending Workspaces, Content Moderation, or related contrib modules

Outline

Workspaces was mostly viewed as a content staging feature. That is still true, but it is no longer the whole story.

Workspaces is now stable in Drupal core and already useful for real publishing workflows. What makes it more interesting now is how it connects with Content Moderation, contrib experimentation, and AI governance.

This session will start with why content staging is still a core enterprise CMS need and what Workspaces in core already gives Drupal teams today. From there, it will look at the current direction around Content Moderation, especially where Workspaces can support more complete publishing flows when changes involve more than one entity.

The session will also cover the role of the Workspaces Extra module as a place to extend and experiment on top of core. Topics will include configuration staging with `wse_config`, workspace previews with `wse_preview`, revert options as a practical fallback, and future plans for these features. Hint: Some of them may even reach Drupal core by Rotterdam! ;)

The final part of the session will look at AI governance. If agents help make content or config changes, those changes should not go directly to live unless intended. This is where Workspaces, Workspaces Extra, and `tool_workspace` can support a more governed, human-in-the-loop workflow.

The session will close with the direction around conflict management, what is already usable today, and what Drupal developers should be watching next across core and contrib.

Learning Objectives

By the end of this session, participants should be able to:
* Understand where Drupal Workspaces fits today in core
* Identify where contrib, especially Workspaces Extra, extends the Workspaces model in practical ways
* Understand why config staging matters for AI governance
* See how Workspaces can support a human-in-the-loop approach for AI and tool-driven changes
* Evaluate which parts of this space are ready now and which parts are still evolving

Experience level
Anyone