Next.js

If you take a look at the pros and cons of decoupled/headless CMS, “no visual preview” is at the top of every list of 'cons'. When we set out to build

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.

On a couple of recent Next.js projects, the design called for highlighted excerpts to be displayed in the search results:

We are! DrupalCon Portland is next week, and we are excited to see you all there in person for the first time in two ...

Chapter Three has been working to ensure our Next-Drupal product is the best solution it can be, and so we're thrilled to announce that Chapt...

You are ready to make your Drupal site headless; what do you need to know about hosting? Hosting a decoupled Drupal site means you are using two different types of hosting technologies—on...

In some upcoming posts, we'll provide more details about the practical steps to implementing Next-Drupal. For now we present eight excellent reasons...

Drupal multisite is the method used to host many sites using one Drupal installation.  This concept and ability have been around since the beginning of Drupal.  It solved lots o...

Ok, sounds weird, but it’s true. Imagine for a moment using Next.js as the decoupled front-end of your Drupal site. Imagine it worked well and was transparent to your content editors. Use...