Blog

At Dripyard, we’ve been focused on making our components work seamlessly in both Drupal and Canvas. One of the trickier challenges was creating an image component that supports both systems while following best practices for performance and accessibility. Here’s how we did it.

Next week will be my first trip to Vienna and I’ve already started planning out the trip, booking train tickets, purchasing eSims, etc! I’m soooo excited. I’ll be presenting two sessions at next week’s DrupalCon Europe.

We’re thrilled with the turnout for our Dripyard themes product launch! The response has been incredibly encouraging as we kick off this new venture.

Dripyard’s product launch webinar is coming up in less 7 days 😅!

Dripyard builds premium Drupal themes that rely only on core, with no contrib modules, external libraries, or companion modules. A custom class loader ensures clean structure, modern PHP, and consistent autoloading, while features like Layout Builder support, recipe installation, and inheritable theme settings make our themes flexible, maintainable, and easy to extend. In this article, we share the hurdles we faced and how we solved them.

Andy and I joined the hosts to talk about why we launched Dripyard, what makes our premium Drupal themes different, and how Drupal’s modern tooling like Single Directory Components and Drupal CMS (Canvas + Recipes) have made this the perfect time to bring high-quality themes to the ecosystem.

Theming in Drupal has historically been expensive and complex. Unlike WordPress or Webflow, you can’t just drop in a template and go. A proper Drupal theme requires specialized knowledge.

You’ve probably heard, “The first rule of ARIA is don’t use ARIA". This is a tongue-in-cheek reference to the movie Fight Club, but the reality is more nuanced.