If you've been building Drupal sites for a while, you know the pattern: a new requirement comes in, you reach for a custom or dust off an aging contributed module, and before long your code base is a patchwork of narrowly-focused solutions. Over time, maintenance becomes a chore.
There's a better way.
Drupal 8 introduced the plugin system — a big leap toward modularity. Suddenly, we could write small, focused classes to add functionality in a clean, reusable way:
ECA 2 is a major milestone. The main improvements are:
Back in July, we've been so excited about the launch of ECA 1.0.0 after around 3,000 hours of development work in only 12 months, that we didn't even write a blog post at the time. The following weeks, the team was busy dealing with feedback and support, as well as starting to build even more features. That's how 4 months went by, certainly time for a recap of what has been happening and what ECA brings to the Drupal project and its community.
ECA stands for "Events - Conditions - Actions" and is a powerful, versatile, and user-friendly rules engine for Drupal 9+. The core module is a processor that validates and executes event-condition-action plugins.
Development in ECA has been intense over the last 4 months, since we first presented this new
