The current could be improved to engage better with non-Drupal users visiting the project page. Instead of talking about technical implementation, the opening section should focus on examples and outcomes. Below is a suggested improvement. ```html <div class="markdown-to-html"> <p><strong>ECA is a visual automation and orchestration platform for Drupal.</strong></p> <p>ECA enables teams to model workflows, business rules, approvals, content behavior, integrations, and AI-powered processes without writing custom code. Similar to well known SaaS platforms, ECA allows you to automate how your Drupal site behaves through a visual workflow builder.</p> <p>Unlike generic automation platforms, ECA is deeply integrated into Drupal itself — including content, users, forms, permissions, workflows, APIs, and Drupal's extensible ecosystem. This allows organizations to replace large amounts of bespoke glue code with transparent, maintainable, and deployable workflows.</p> <p>Under the hood, ECA processes event-condition-action models: when a Drupal event fires, ECA evaluates conditions and executes actions accordingly. Combined with a visual modeler, ECA lets you build sophisticated automation workflows without writing code.</p> <h3 id="user-content-upgrading-from-eca-2">Upgrading from ECA 2<a href="#upgrading-from-eca-2" aria-label="Link to heading 'Upgrading from ECA 2'" data-heading-content="Upgrading from ECA 2" class="anchor" rel="nofollow"></a><br> </h3> <!-- existing content continues unchanged --> ``` In addition to updating the introduction, the how it works section could also be improved: ```html <h3 id="user-content-how-it-works">How it works<a href="#how-it-works" aria-label="Link to heading 'How it works'" data-heading-content="How it works" class="anchor" rel="nofollow"></a><br> </h3> <p>ECA orchestrates how Drupal's subsystems work together. It listens to Drupal events, evaluates conditions, and executes actions based on your workflow models. ECA builds on Drupal's existing architecture — including events, actions, plugins, queues, workflows, forms, and APIs — while providing a visual layer for modelling automation and business logic.</p> <p>Models are stored as Drupal configuration, making workflows fully deployable through standard configuration management, recipes, and Drush.</p> ```