bluedrop.fr becomes a Drupal Certified Partner

We could just announce it: we have earned enough credits to become a Drupal Certified Partner. These credits are awarded by Drupal based on different markers of commitment and expertise: certifications, recognized skills, contributions to the community, participation in the ecosystem... In other words, this status can't be obtained just by filling out a form: it is built over time.

It's done. And we are proud of it.

But what brings us the most joy is the whole story behind this badge:

• over 20 years of digital projects,

• developers who have learned, tested, broken, started over,

• clients who have entrusted us with increasingly ambitious projects,

• open source contributions, conferences, and passionate discussions,

• and also a lot of time spent looking for ways to do better.

Of course, at the time, Drupal did not yet occupy the place it holds today in the CMS landscape. Since 2004, we have supported organizations of very different sizes and sectors in the design, development, redesign, and maintenance of their digital platforms. We have seen several generations of Drupal come and go, changed our methods, learned from our mistakes, contributed to modules, developed our own tools, and kept up with ecosystem developments. Migration, redesign, multisite, multisite factory, performance, accessibility, security, integration with third-party systems, maintenance, and evolution: our expertise has been built project by project. Today, 95% of our developments are done with Drupal.

This figure says a lot in the end. It proves that we are not a generalist agency that offers Drupal when it appears in a specifications document. It shows that we have chosen to make this technology our specialty and that we have had the time to get to know its strengths, its subtleties... and its little quirks.

This is probably one of the aspects we care about the most.

Drupal is open source. This means we can use software built and improved by a global community, rely on their work, contributions, modules, and expertise.

So, naturally, at some point, it's only fair to give back.

Over the years, our teams have contributed to more than 20 modules and Drupal projects. Some were born from a problem encountered on a client project. Others from a developer's frustration, which is a great driver for innovation!

Among them, Deindex Unpublished Files, used by more than 50 reported Drupal sites , addresses a fairly simple but important problem: preventing files linked to unpublished content from remaining publicly accessible or being indexed by search engines.

Another contribution: Page Cache Exclusion, used by more than 500 reported Drupal sites . The module gives more control over Drupal's page cache and notably helps prevent unnecessary cache entries from unnecessarily querying the database.

They may not be the most glamorous modules in the Drupal ecosystem. But they solve real problems. And that's exactly what we love about open source: starting with a real problem, finding a solution, realizing that someone else might need it too, and sharing it.

This desire to search, test, and share is also found in our R&D projects.

With DropFactory, for example, we wanted to address a very concrete issue: how to continue efficiently managing and industrializing a fleet of Drupal sites?

The project was born notably after the end of Aegir, which until then had fulfilled this role, and whose discontinuation left some of our clients without an equivalent solution.

So we started searching. Then developing. Then testing. And DropFactory gradually took the form of a true console that allows you to manage a Drupal site factory.

We presented DropFactory at the DrupalCamp Grenoble in 2026, with a fairly simple idea behind this presentation: to show what we had built, but above all to open the project to feedback, criticism, and community testing.

This same logic led us to develop our Starter Drupal, our in-house technical base designed to accelerate the launch of web projects.

After more than 20 years of building Drupal sites, we have accumulated a great deal of best practices. It would have been a shame to let them sit unused in our developers’ heads or in dozens of Git repositories. So we built a foundation that incorporates our approaches to development, performance, accessibility, security, and eco-design.

The idea isn’t to make all projects fit the same mold. In fact, it’s quite the opposite. By industrializing what can be industrialized, we free up time for what can’t be: business needs, user experience, content, specific integrations. In short, the real differentiating points of a project.

So yes, we are now Drupal Certified Partner (and yes, we will probably display the badge proudly).

But what really matters to us is everything behind it: 20 years of Drupal, 95% of our development done with the platform, 7 developers with a Vetted role on Drupal.org, 2 developers certified by Acquia, over 20 open source contributions, events supported and attended, and R&D projects shared with the community.

A story that began over 20 years ago and continues to be written with our teams, our clients, our contributors, and everyone we meet along the way.

Drupal has changed. Our professions have too. The tools will continue to evolve, probably more and more quickly.

We simply want to keep being part of the adventure.

See you soon, somewhere between two lines of code, a DrupalCamp, and a coffee.