Technology & Innovation

A/B testing traditionally requires expensive third-party platforms, complex JavaScript integrations, or extensive custom development. But what if you could build a native, context-aware A/B testing system directly in Drupal—one that leverages your existing design system, automates variant creation, and uses AI to intelligently manage experiments?

By combining Figma’s design variants, Make’s automation capabilities, and Model Context Protocol (MCP) for intelligent orchestration, we can create a powerful A/B testing workflow that feels native to Drupal while remaining accessible to designers and marketers.

As AI tools become increasingly integrated into development workflows, a fundamental challenge has emerged: how do AI assistants effectively interact with complex, domain-specific systems like content management platforms? Model Context Protocol (MCP) offers an elegant solution that’s particularly relevant for Drupal developers.

What is Model Context Protocol?

Model Context Protocol (MCP) is an open protocol developed by Anthropic that standardizes how AI assistants connect to external data sources and tools. Think of it as a universal adapter that allows AI models to interact with your systems in a structured, secure, and contextually aware manner.

At the 2024 Pacific Northwest Drupal Summit, MindSing sponsored a session exploring the practical integration of AI tools into modern development workflows. The session, “Tip-Toeing into the Deep: Seek, Prompt, Repeat,” demonstrated how developers can leverage AI assistance while maintaining code quality and deepening their expertise.

The AI Development Revolution

We’re in the midst of a fundamental shift in how developers work. Tools like GitHub Copilot, ChatGPT, Claude, and specialized coding assistants are no longer experimental novelties—they’re becoming integral parts of professional development workflows.

Automated testing is often viewed as a “nice to have” in Drupal development—something teams plan to implement “when there’s time.” But treating testing as optional is a costly mistake. The reality is that automated testing is fundamental to building maintainable Drupal applications, reducing bugs, and enabling teams to refactor and upgrade with confidence.

This guide will walk you through the essentials of automated testing in Drupal, from basic concepts to practical implementation, helping you build a testing practice that actually fits into your development workflow.

In the rapidly evolving landscape of web development, choosing the right foundation for your digital infrastructure is more critical than ever. At MindSing, we’re passionate advocates for open source technologies—particularly Drupal—and here’s why.

The Power of Open Source

Open source software represents more than just freely available code. It embodies a collaborative philosophy that drives innovation, ensures transparency, and provides long-term sustainability for your digital investments.

Transparency and Security

When you build on open source platforms, you’re not locked into a proprietary black box. Every line of code is inspectable, auditable, and verifiable. This transparency is crucial for enterprise organizations and higher education institutions that must maintain strict security and compliance standards.

If you’ve been building front-end applications for the past decade, Webpack has probably been a constant companion—sometimes helpful, often frustrating, occasionally infuriating. Those 30-second (or 3-minute) build times. That sprawling configuration file that no one fully understands. The mysterious “Module not found” errors that appear only in production.

Then you hear about Vite. Cold server starts in milliseconds. Hot module replacement that actually feels instant. Configuration so simple you wonder if you’re missing something.