Building Drupal AI as Vardot's Full-Time Contributor

I'm an engineer by education, a Drupal developer by profession, and a gamer by passion. My childhood passion for gaming is what drove me into AI, as gaming was one of the major early drivers of AI.

When Vardot joined the Drupal AI Initiative as a Gold Sponsor, the company committed one full-time contributor to the work. That contributor is me. For the last several months, I have been building AI into Drupal alongside developers from more than 30 partner organizations around the world.

What Is It Like Inside the Drupal AI Initiative?

It is a distributed team of more than 50 developers who have never sat in the same room. On any given month, that many people are actively contributing across companies including 1xINTERNET, Acquia, FreelyGive, Salsa Digital, Pantheon, QED42, Kalamuna, and Tag1 Consulting.

We coordinate through online channels and a shared resource-planning sheet that tracks who is doing what each month.

What surprised me most was how different the working styles are across companies. We discuss, we negotiate, and the code that ends up shipping is usually better for it.

What Does a Full-Time Drupal AI Contributor Actually Build?

Modules, mostly, and the plumbing underneath other people's modules. My contribution record on drupal.org shows more than 86 credits across the Drupal AI ecosystem as of August 2026, spread across the AI core module, AI Agents, AI File to Text, AI Logging, Document Loader, and the Context Control Center.

Document Loader: Consistent Document Ingestion for Drupal AI

Document Loader gives Drupal a consistent, plugin-based way to ingest documents from any source: PDFs, CSV files, Word documents, spreadsheets, HTML pages, APIs, and Parquet files.

Before this module existed, every developer who needed to load documents into Drupal for AI had to write their own ingestion logic. That meant duplicated effort across the ecosystem and inconsistent results when AI agents tried to read the data.

Document Loader 2.0.0 shipped on 19 March 2026. I worked on the release alongside Nick Opris and Rob Loach (Kalamuna), building on architecture work that started inside the Context Control Center effort led by Marcus Johansson at FreelyGive. I am now a co-maintainer of Document Loader, along with AI File to Text, AI Agents Debugger, and Unstructured.

AI Core Module: Guardrails, Scaffolding, and Editor Integration

On the AI core module itself, my record shows 27 contribution credits over the past year. That work falls into three buckets:

• Guardrails. Input-length limits to defend against denial-of-wallet attacks, multi-guardrail-set support on InputInterface, and schema fixes.
• Agent skills and Drush generators. Scaffolding for AI Provider plugins, Field Widget Action plugins, API Explorer plugins, Automator Type plugins, and Guardrail plugins.
• Editor integration. MDX editor event support and the tooltip component for the AI Dashboard.

AI 1.4.0 pulled most of this together: streaming-aware guardrails, structured-content validators, and improvements to the entity reference automator.

Numbers aside, the part I'm proudest of is that Document Loader unblocked work on several other modules that were waiting on it. When you're building infrastructure, the success metric isn't your own feature shipping. It's how many other people can finally ship because of what you built.

How Did My Vardot Background Help?

Four years at Vardot is what made this work possible, mostly through the review discipline.

Vardot's engineering culture is built around high standards and heavy automation. Every change goes through a structured review process. It's the kind of discipline that feels slow on a Monday and pays off on a Thursday when something in production doesn't break.

When I joined the Drupal AI Initiative, I started working alongside senior developers from around the world. The thing that kept me steady was the muscle memory from those four years, and the fact that Vardot is a Drupal Diamond Certified Partner with that level of practice behind every line of code we ship.

What I gained from the initiative, on top of what I already had, is hands-on experience designing and building AI agents, end-to-end guardrails, plugin scaffolding, document ingestion, and automator integration. It's a skill set I cherish and continue to develop.

Why Does Drupal Work Well for AI?

Because the structure an AI agent needs is already there. Drupal is object-oriented and structured. When I write an AI agent that needs to read or modify content, I'm not writing prompts that try to wrestle blob text into a usable shape. I'm working with entities, fields, and a permission system that already exists. The agent operates inside the guardrails the platform provides, not guardrails I have to invent.

The other thing I notice every day: the AI module ecosystem is designed the way Drupal designs everything else, as plugins and entities rather than as a layer sitting on top. That consistency is why it composes properly with the rest of the platform.

This is what people mean when they say Drupal AI is production-ready. It's not that it's perfect. It's that the foundation is solid enough that you can put it in front of real editors at real organizations without being afraid of what happens next. It's also why those same modules can ship inside Varbase, our Drupal distribution, and behave predictably from day one.

How Has AI Changed the Work of Development?

It has compressed the writing and debugging, and left everything else where it was. I write code faster. I debug faster. The parts of a day that used to go into boilerplate and stack traces now go somewhere more useful.

But the work of building real software is still detailed, structured, and meticulous in a way AI can't fully match yet. Every pull request still goes through human review. AI accelerates the work, but it doesn't replace the engineer doing it. On a codebase this many people depend on, the review is not the bottleneck to be optimized away. It is the thing keeping the ecosystem coherent.

What Am I Working Toward?

I set goals the same way I do as a gamer. Pick the next milestone, make it specific, work toward it, and don't stop until it's hit.

Right now, my goal is to make Vardot's contribution to the Drupal AI Initiative a real, visible part of our track record in the Drupal community, and to see Drupal AI itself reach its full potential as the leading open-source AI-powered CMS.

I'm already past the first checkpoint. The modules I co-maintain are downloaded and used. The credits on my profile keep going up. The next checkpoint is the next release. And the one after that.

How Can You Start Contributing to Drupal AI?

You do not need to work at a partner organization. Two routes exist, and only one of them requires a sponsorship.

• Contribute directly. The prioritized backlogs live on Drupal's GitLab instance and any Drupal contributor can pick up issues. This is how most people start.
• Join as a partner organization. Partners pledge people and funding, attend the regular partner meetings, and help set the backlog priorities. That is the route Vardot took.

If you want a specific place to begin: the modules I co-maintain all have open issues, and infrastructure work like document ingestion tends to be undersubscribed relative to how much depends on it. Issue queues are public, and so is every credit that comes out of them.