--- title: "DDD 2026: AI in Drupal development, beyond the hype and with ethics" url: "https://www.sparkfabrik.com/en/blog/drupal-ai-development-ethics-ddd2026/" lang: "en" type: "blog-post" date: "2026-04-28" lastmod: "2026-04-28" author: "SparkFabrik Team" description: "The integration of language models into the open source CMS is moving past the experimental phase to become solid architecture. We analyze how the community is defining ethical and technical standards to govern automation. Digital sovereignty drives the development of production-ready solutions." tags: ["AI","Drupal","Open Source","SparkFabrik"] schema: "@context": "https://schema.org" "@type": "BlogPosting" "headline": "DDD 2026: AI in Drupal development, beyond the hype and with ethics" "description": "The integration of language models into the open source CMS is moving past the experimental phase to become solid architecture. We analyze how the community is defining ethical and technical standards to govern automation. Digital sovereignty drives the development of production-ready solutions." "url": "https://www.sparkfabrik.com/en/blog/drupal-ai-development-ethics-ddd2026/" "datePublished": "2026-04-28T00:00:00+00:00" "dateModified": "2026-04-28T00:00:00+00:00" "author": "@type": "Person" "name": "SparkFabrik Team" "image": "https://www.sparkfabrik.com/images/blog/ddd-2026-l-ai-nello-sviluppo-drupal-oltre-l-hype-e-con-etica/featured.webp" "publisher": "@type": "Organization" "name": "SparkFabrik" "url": "https://www.sparkfabrik.com" "logo": "https://www.sparkfabrik.com/images/logo.svg" --- # DDD 2026: AI in Drupal development, beyond the hype and with ethics **Author:** SparkFabrik Team **Published:** 28 April 2026 **Tags:** AI, Drupal, Open Source, SparkFabrik --- {{% tldr %}}Drupal Developer Days 2026 marked the transition of artificial intelligence from hype to an architectural pillar, focusing on performance and digital sovereignty. Through tools such as Symfony Messenger, the AI 2.0 module, and the no-code approach of ECA, the community is redefining Drupal development. You will learn how to integrate autonomous agents securely, optimizing Cloud Native infrastructure to ensure scalability, resilience, and technical training that values human talent beyond simple automation.{{% /tldr %}} The **Drupal Developer Days (DDD) 2026 in Athens** showcased an open source ecosystem focused on structural engineering. Text generator demos have given way to concrete implementations. The community is actively deciding the rules of engagement for integrating large language models, favoring a solid architectural approach over passive adoption. **Artificial Intelligence was the cross-cutting protagonist of the event**, viewed through the lens of technical pragmatism. Discussions covered AI as an advanced development tool, as a social phenomenon impacting team training, and as an opportunity to redefine the boundaries of the CMS. If you want to understand the starting point of this evolution, [discover our complete overview of AI features in Drupal](/en/blog/drupal-ai-panoramica-novita-visione-di-sparkfabrik/). The message emerging from the Greek capital is clear: Open Source today represents a solid guarantor of digital sovereignty in a market driven by proprietary vendors. **SparkFabrik participated by bringing real code** and production-ready solutions to the stage, demonstrating that innovation is driven by solving complex problems. ## Day 1 - The infrastructure of innovation and extreme performance The integration of AI into Drupal is changing the very architecture of the system, requiring solid DevOps foundations. Technical sessions by **Frederik Wouters**, focused on Autonomous Drupal, voice commands, and conversational interfaces, and by **Marcus Johansson**, focused on the AI module 2.0, Guardrails, and the shift toward Symfony AI, charted the course. We are talking about an intelligence layer capable of orchestrating complex processes, analyzing context, and suggesting structural optimizations. This ambition faces the physical limits of infrastructure. AI requires an underlying ecosystem capable of handling anomalous computational loads, where database performance remains the fundamental bottleneck. Moving from 20 seconds to 500 milliseconds for loading a complex view is pure data engineering. **Robin Colombier**'s talk addressed the latency problem through the strategic use of materialized views on PostgreSQL. Instead of calculating complex queries in real-time with every request, data is pre-calculated and stored, updating only when necessary. > Artificial intelligence does not forgive fragile architectures. If the database is not optimized, adding AI agents in the background risks overloading the system under the weight of concurrent queries. This optimization is a prerequisite for effective AI implementation. When an autonomous agent needs to analyze thousands of nodes to vectorize content, the database must respond in milliseconds. To support this horizontal scalability and manage load spikes generated by asynchronous operations, traditional on-premise infrastructure quickly shows its limits. In this context, [explore the benefits of the Cloud Native approach for scalability](/en/blog/guides/guida-completa-cloud-native/), an architectural paradigm that allows for decoupling services and dynamically scaling computing resources exactly where they are needed. ### Drupal AI 2.0: architecture and adoption status Marcus Johansson outlined the status of the AI module and plans for version 2.0. Adoption is measurable: as of April 12, 2026, the AI module reached 13,980 active installations on [Drupal.org](https://new.drupal.org/project/usage/ai). ![Marcus Johansson and Drupal AI 2.0](/images/blog/ddd-2026-l-ai-nello-sviluppo-drupal-oltre-l-hype-e-con-etica/inline-0-en.webp) The architecture is undergoing profound evolution, with the adoption of Symfony AI as a unified abstraction layer. On the security front, the **Guardrails system** is fully operational, preventing models from exposing personal data, generating out-of-context content, or responding to dangerous prompts (a contribution from SparkFabrik). Two ready-to-use recipes are also already available: ai_recipe_guardrails_pii, which blocks emails, phone numbers, IBANs, and credit cards, and ai_recipe_guardrails_prompt_safety, which covers legal or medical advice, dangerous HTML, and code injection. Both can be installed with a single `drush recipe` command, offering a concrete and rapid implementation for those who want to start without building the configuration from scratch. Furthermore, one of the ongoing developments is **MCP (Model Context Protocol)** support, which will transform Drupal into a tool queryable by external AI agents like Claude or Cursor. The maintainer of the Drupal MCP Client module is our own Roberto Peruzzo. The first day therefore highlighted a practical principle: before implementing AI in the application layer, it is necessary to modernize the data layer and hosting infrastructure. But the day did not focus only on code. There was also a broader perspective to consider. Opening the day, in fact, was a fireside chat between **Dries Buytaert** and **Prof. Dimosthenis Anagnostopoulos**, Secretary General for Digital Transformation of the Greek government. It is not common to see a government representative on the stage of an open source developer conference. It is a signal: the topics the community has been discussing for years, such as digital sovereignty, control over infrastructure, and the risks of vendor lock-in on proprietary models, are entering the European political agenda. Open Source confirms itself as the guarantor of institutional control over data, a critical theme that invites you to [delve into the importance of digital sovereignty in open source](/en/blog/drupal4goveu-sovranita-digitale-e-open-source-per-la-pa/). ## Day 2 - Automation, site building, and the evolving ecosystem The second day shifted the focus from the database to the presentation and automation layer, highlighting the ongoing evolution in developer experience. **Pierre Dureau**'s session turned the spotlight on [Display Builder](https://www.drupal.org/project/display_builder). In particular, it focused on HTMX, a technology gaining traction in the community for its ability to modernize the frontend without introducing the complexity of heavy single-page application (SPA) frameworks like React or Vue. ![Pierre Dureau, Display Builder and HTMX](/images/blog/ddd-2026-l-ai-nello-sviluppo-drupal-oltre-l-hype-e-con-etica/inline-1-en.webp) HTMX allows for dynamic and partially updatable user interfaces by working directly with HTML rendered by the server. This approach reduces the cognitive load for development teams, keeping business logic anchored to the Drupal backend. In combination with emerging tools, interface creation becomes a fluid and modular process. In this regard, the ecosystem is being enriched with advanced visual solutions; an excellent example of this evolution is documented in [Michael Fanini's talk on Display Builder](https://www.youtube.com/watch?v=jjYtRA0uIUY) during our own event **Drupal X Business**. Parallel to the evolution of the frontend, the backend is experiencing an event-driven update. **Jürgen Haas**'s talk on ECA (Event Condition Action) showed how no-code and low-code automation is evolving natively within Drupal. ECA allows site builders to configure complex workflows, such as sending notifications based on specific triggers or manipulating entities, without writing a single line of custom PHP. This accessibility of business logic is an important step. If AI is to interact with Drupal, it will increasingly do so by triggering events that the ECA system can intercept and manage. ![Jürgen Haas's talk on ECA](/images/blog/ddd-2026-l-ai-nello-sviluppo-drupal-oltre-l-hype-e-con-etica/inline-2-en.webp) At the recent DrupalCon Chicago, a figure regarding ECA emerged that makes all of this very concrete: Jürgen, as a **senior developer and orchestrating advanced AI tools**, wrote, validated, and documented 90,000 lines of code in just six weeks. This is not an experiment: it is a contrib module in production, used by thousands of sites. The data shows that **AI as a skill amplifier** is not an abstract concept, but is already measurable. We also discussed this in our article on the [agentic-first approach to Drupal development](/en/blog/sviluppo-drupal-e-ai-il-nuovo-approccio-agentic-first/). Also very interesting was the talk by **Klaus Purer**, who presented Mago, a new PHP tool that can check coding standards and code issues in seconds. The ecosystem is maturing to provide teams with tools that abstract technical complexity, allowing developers to focus on architecture and the integration of advanced services. If you want to understand how these tools fit into the overall platform strategy, [explore the evolution of Drupal CMS toward no-code](/en/blog/drupal-cms-la-rivoluzione-no-code-nel-web-development/). ## Day 3 - Ethics, SDC, and SparkFabrik's contribution Technology without direction only produces technical debt. The third day of DDD opened by addressing the responsibility that comes with adopting AI, starting with Ifrik's keynote on ethics. The community discussed the problem of bias in training datasets and the social impact of automation. These are not abstract discussions, but engineering decisions: how do we structure permissions so that an AI model does not expose sensitive data? How do we ensure that generated content is accessible and inclusive? On the frontend development front, the push toward modularity found confirmation in the talks by **David Galeano** on advanced agentic workflows and FlowDrop, and **Anand Toshniwal** on Single Directory Components (SDC). SDCs support the developer experience: grouping markup, styles, and JavaScript logic into a single directory facilitates maintenance and the work of AI agents, which can analyze and generate isolated components with greater precision. ### Symfony Messenger and Drupal Queues: SparkFabrik's talk Technological leadership is demonstrated by writing code and defining standards. **SparkFabrik's contribution** to this architectural evolution came with **[Luca Lusso's talk on Symfony Messenger](https://devdays2026.drupal.org.gr/drupal-developer-days-athens-2026/session/supercharge-your-drupal-queues-symfony-messenger)** and its integration into Drupal via the `sm` module (drupal.org/project/sm), an example of how we want to make a difference by tackling real problems. ![Our Luca Lusso presenting his talk on Symfony Messenger and Drupal Queues](/images/blog/ddd-2026-l-ai-nello-sviluppo-drupal-oltre-l-hype-e-con-etica/inline-3-en.webp) Integrating artificial intelligence models requires external API calls that can take seconds to respond or fail due to network timeouts. Blocking the main PHP process while waiting for a response from OpenAI or Anthropic means compromising site performance. The `sm` module solves this problem, allowing heavy tasks to be delegated to asynchronous message queues managed by background workers. This approach ensures resilient pipelines, with automatic retry logic in case of API failure, keeping the user interface responsive. It is a demonstration of how SparkFabrik tackles enterprise bottlenecks by releasing open source solutions for the entire community. To see how we bring these skills to the stage, [watch our tech talks and interventions at international conferences](/en/risorse/video/). Solving complex asynchronous problems is the foundation upon which AI-based applications are built. ## The human impact: training and AI as a skill amplifier Interest in new architectures goes hand-in-hand with the challenge of talent sustainability. During the three days in Athens, the debate on **mentoring in the AI era** occupied a central space. If generative artificial intelligence is capable of instantly writing boilerplate, configuring routes, and drafting unit tests, how will new developers learn the fundamentals of the framework? The risk is the atrophy of problem-solving skills. A junior who merely accepts AI suggestions without understanding their architectural implications will struggle to intervene when systems fail in production. The response that emerged from the community is that AI must not replace human mentoring, but transform into a support tool. Continuous training therefore becomes a widespread priority, which does not only concern junior profiles. Even senior developers and tech leads must learn to **govern AI**, using it as a digital mentor to explore new languages or to perform complex refactoring, while maintaining control over domain logic. The goal is to **develop critical thinking**, shifting the focus from syntax to the design of secure and scalable systems. Software engineering is not about typing code quickly, but about making correct architectural decisions. AI accelerates typing; the human must ensure the direction. This is the approach we have formalized in our [AI Vision](/en/chi-siamo/ai-vision/): AI as a tool for augmentation, not replacement. > The best technology is born from the harmony between deep technical skills and solid human relationships. In this scenario, on one hand, the need to implement a solid AgentOps approach for the orchestration of autonomous agents emerges, while on the other, the choice of Open Source technologies takes on strategic value. Maintaining control over one's data, training models, and delivery infrastructure helps avoid the vendor lock-in imposed by large tech players, ensuring digital sovereignty, a critical issue especially for public administrations and large European enterprises. ## Conclusion The Drupal Developer Days in Athens showed how Artificial Intelligence in the Drupal world is integrating as an architectural requirement, pushing the community to adopt Cloud Native paradigms, asynchronous code, and optimized interfaces. The future of Drupal is hybrid. On one hand, it requires technical efficiency to support autonomous agents and automations; on the other, it demands human responsibility to govern data ethics, accessibility, and team training. There is no sustainable innovation without rigorous control over software quality and supply chain security. The community has demonstrated once again that Open Source is not just technology: it is the way collective trust is built around shared choices, as [explored in our vision on agentic-first Drupal development](/en/blog/sviluppo-drupal-e-ai-il-nuovo-approccio-agentic-first/). We were there, we contributed with real code, and we are already looking forward to the next appointment with the community at [Drupal Developer Days Valencia 2027](https://devdays2027.drupal.es/). But before that, see you at [DrupalCamp Italy 2026](https://www.drupalcampitaly.it/)!
Drupal Development and Consulting. Tell us about your Project
--- ## Frequently Asked Questions ### How is AI changing custom module development in Drupal? AI accelerates the writing of boilerplate and test automation, but requires rigorous human review. Tools like the AI module 2.0 allow LLMs to be integrated directly into the CMS, shifting the developer's focus from syntax to architecture and data security. ### What is the `sm` module presented at Drupal Developer Days? The `sm` (Symfony Messenger) module, presented by Luca Lusso of SparkFabrik, is a solution for managing asynchronous operations and message queues in Drupal. It allows heavy tasks to be delegated to the background, drastically improving application responsiveness and user-perceived performance. ### Which talk did SparkFabrik give? SparkFabrik actively participated with Luca Lusso's talk dedicated to Symfony Messenger and its integration into Drupal via the `sm` module. The talk illustrated how to manage asynchronous operations and message queues to delegate heavy tasks to the background, ensuring resilient pipelines and improving overall application performance. ### Why is HTMX gaining popularity in the Drupal community? As discussed by Pierre Dureau in Athens, HTMX allows for dynamic and responsive user interfaces by working directly with HTML rendered by the server. This reduces frontend complexity, decreasing cognitive load for teams and improving overall performance. ### Will the use of AI replace junior developers? No, but it will change their training path. The consensus reached at DDD is that AI should function as a skill amplifier. The challenge for companies is to use AI to accelerate the learning of all collaborators, while maintaining the focus on a deep understanding of the core. --- ## Related Articles - [Why CTOs choose Drupal: AI, sovereignty, and platform engineering](https://www.sparkfabrik.com/en/blog/why-ctos-choose-drupal-enterprise/) - Modern enterprise architectures require solid foundations to manage critical data and complex … - [Drupal AI 1.3: security, governance, maturity and new tools](https://www.sparkfabrik.com/en/blog/drupal-ai-1-3-security-governance/) - The adoption of LLMs in CMSs requires solid architectures to avoid privacy risks and hallucinations. … - [Drupal development and AI: the new agentic-first approach](https://www.sparkfabrik.com/en/blog/drupal-ai-agentic-first-approach/) - Source code is becoming a disposable resource. The true value in Drupal development is shifting … --- *This is a Markdown version of the blog post to facilitate reading by AI and crawlers.* *Visit [https://www.sparkfabrik.com/en/blog/drupal-ai-development-ethics-ddd2026/](https://www.sparkfabrik.com/en/blog/drupal-ai-development-ethics-ddd2026/) for the full version with images and formatting.*