Jürgen Haas Reflects on ECA’s UX-Driven Transformation in Drupal

Questions around usability and long-term adoption reshaped the direction of Drupal’s ECA project over the past ten months, according to a retrospective published by Jürgen Haas. The article traces how discussions with Drupal founder Dries Buytaert during mid-2025 prompted a broader reassessment of how workflow automation should function inside Drupal CMS, particularly for site builders and editors unlikely to interact directly with complex visual modelling interfaces.

Haas describes a shift away from workflow systems centred primarily around standalone visual modelers toward what he calls “in-context customization”. Rather than requiring users to enter separate automation interfaces, the approach attempts to surface workflow controls directly inside existing Drupal administrative workflows. According to the article, the redesign effort was heavily influenced by UX research and user testing conducted with Emma Horrell, Mark Dodgson, and Drupal Canvas architect Lauri Timmanee.

The post also documents substantial technical changes around ECA’s workflow tooling. Haas states that the project rebuilt its Workflow Modeler using React Flow and TypeScript while adding WCAG AA accessibility support, structured YAML editing, drag-and-drop token handling, dark mode support, and live workflow testing and replay functionality. The article additionally discusses the evolution of the Modeler API, which attempts to separate workflow ownership from workflow editing interfaces across multiple Drupal automation scenarios.

Broader orchestration themes feature prominently throughout the article. Haas positions ECA as one component within a wider Drupal orchestration ecosystem involving FlowDrop, Maestro, Drupal CMS, MCP integrations, AI-assisted workflows, and external automation services. The article argues that Drupal’s automation tooling is moving toward integrated orchestration patterns rather than isolated workflow utilities.

The retrospective also highlights collaboration patterns behind the project’s recent development cycle. Haas credits UX researchers, maintainers, early adopters, accessibility contributors, and FlowDrop maintainer Shibin Das for helping reshape the project’s direction through sustained feedback, testing, and coordination. DrupalCon Europe 2025 in Vienna, DrupalCon North America 2026 in Chicago, and Drupal DevDays Athens 2026 are all identified as important milestones in the project’s public evolution.

The article further examines sustainability challenges surrounding rapid contrib innovation inside Drupal. Haas notes that the pace of development depended on a combination of funded work, volunteer effort, community collaboration, and UX partnerships that may be difficult to sustain long term without broader ecosystem support.

The post is the first instalment in a planned nine-part series titled ECA: The Next Chapter, which will further examine workflow orchestration, Modeler API architecture, AI integrations, accessibility work, and long-term sustainability questions around Drupal automation tooling.