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's ECA module has been released 3 years ago, and provides an incredible workflow automation and orchestration platform together with an intuitive UI based on BPMN diagrams. Other complex configuration requirements can now be managed with the same tools as the newly introduced Modeler API provides the framework to serve applications like ECA or AI Agents with modern, exchangeable UIs without having to re-implement any of those ever again.
The Modeler API is a new module that has been created by the Drupal community to address the requirement of existing modules and ecosystems with complex configurations, providing modern and easy-to-use UIs for non-technical users so they can independently create, modify, and maintain their own sites. Examples of such ecosystems are ECA (Events, Conditions, Actions - Drupal's modern rules engine), AI Agents, and Migrations.
Protecting your Drupal sites from unexpected dependency issues requires a proactive approach. This article reveals our strategy for continuously monitoring a suite of reference Drupal sites – automatically updated every hour – to detect runtime problems stemming from dependency updates. We’ll demonstrate how to identify PHP errors, styling issues, and even frontend JavaScript errors that often go unnoticed, ensuring a smooth and reliable experience for your Drupal users.
Keeping your Drupal modules aligned with the latest updates — including changes from Drupal core or other dependencies — is critical. But how do you know if those updates are actually safe? This article shows you how to set up regular, automated testing using GitLab CI to proactively detect upstream changes, ensuring your modules remain compatible and stable before they impact your users. Learn how to identify potential issues early and prevent costly support requests.
Almost 2 years ago, ECA 1.0.0 was published, and a lot happened in the 23 months in between. Today, ECA gets its first major update which comes not only with a ton of new features but also with code clean-up, performance improvements and support for the latest Drupal core releases 10.3 and soon 11.
It's in LakeDrops' genesis: supporting Drupal as a product, Drupal's community and the Drupal Association. This is mutually beneficial since Drupal is the fundamental component of every single LakeDrops project, so giving back is the best possible investment of the company to ensure a prosper and sustainable future.
There are plenty of reasons why an update of Drupal sites based on version 7 to the modern platform of Drupal 9 or 10 can be a challenge. Limited resources come to mind, but more often missing features due to not yet working modules are blocking the otherwise useful update plan. The good news explored in this blog post, thanks to the ECA module those missing features may no longer be holding you back and that's why now is the best time to get started with the Drupal 7 update.
November 2022, Hamburg, Germany: the Splash Awards ceremony was long awaited and ECA made it to the top, together with many other very successful projects from Germany and Austria. Being awarded with a special price for the "Biggest Community Value" is exceptional and this blog post publishes the project application for the Splash Awards because that nicely describes, what makes ECA so exciting.
Time for a recap, 4 months after ECA release 1.0.0 back in July 2022. Hundreds of site using ECA already, extremely positive feedback from the community, new features in the making and honoured with the special "Biggest Contribution Value" award by the German/Austrian SplashAwards 2022. We couldn't have hoped for a better start of the project.