Drupal gives us enormous freedom to build complex digital platforms. But that flexibility also means that seemingly small technical decisions can have a surprisingly large impact on architecture, maintainability, performance, security and, ultimately, the success of a project.
Rather than focusing only on project management, we will explore the technical patterns behind common delivery problems: requirements that look simple but hide significant complexity, configuration that gradually becomes unmanageable, permissions and workflows that grow out of control, integrations that introduce unexpected dependencies, and contributed modules that can either accelerate a project or become a long-term maintenance challenge.
We will also discuss how developers can play a more active role beyond simply implementing tickets: challenging requirements when necessary, communicating technical risks clearly, proposing sustainable alternatives, documenting reusable solutions and turning lessons learned in individual projects into knowledge that can benefit the wider Drupal community.
During the session, we will explore how to:
- Recognise early signs of architectural and technical drift.
- Identify hidden complexity behind apparently simple Drupal requirements.
- Evaluate contributed modules and dependencies with a long-term mindset.
- Make pragmatic decisions between configuration, custom development and contribution.
- Communicate technical risks before they become project blockers.
- Transform project-specific solutions into reusable patterns and community contributions.
- Build Drupal solutions that are easier for the next developer — and the wider community — to maintain and evolve.
The goal is not to eliminate complexity from Drupal projects. It is to understand it earlier, manage it better and share what we learn.
Because the best Drupal projects are not just the ones that go live successfully — they are the ones that leave behind better code, better practices, better developers and, whenever possible, a better Drupal ecosystem.