The web is continuously growing and evolving. As a result, powerful and developer-friendly tools and frameworks are part of the daily work for most front-end developers nowadays.
One of the questions I get asked every other week is “Does next-drupal work with GraphQL?” .
Yes. Both the Next.js Drupal module and the next-drupal package work wit...
It’s not every day you have an opportunity to help rethink and redesign a website that is global in its impact and audience. We've been honored to work on such an important endeavor and s...
Welcome to part two of Hell is Programming a Calendar, where I will dive into some of the more nitty-gritty details about handling time specifically in Drupal. If you haven’t already, I highly rec...
At Chapter Three, we believe that most Drupal websites could gain a performance boost by going headless. While this is how we’re planning to build future Drupal sites, we understand going all in on headless might not be feasible for existing sites. This is why we built next-drupal for progressive adoption.
A project team is managing a site for people to see events in their local community. The client asks the team to make a (seemingly) pretty simple feature; they want logged-in users to be able to ma...
Drupal 7 and PHP’s end-of-life are right around the corner and many people are thinking about the best path forward. The three options tend to be: a.) traditional “Lift and Shift” to Drupal 9, b.) “Lift, Shift and Improve a few things,” and c.) “totally rethink,” and rebuild the site. Each option produces a complex Drupal 9 site. Many Drupal 7 sites are layers of back-end code, complex front-end code, and content types that have evolved over the years.