Next.js

The Chapter Three team is excited to announce the first stable release of Next-Drupal 2.0, offering powerful integration for building decoupled, Next.js-based front-ends with Drupal. This release brings major performance improvements, expanded API capabilities, and a smoother developer experience, reinforcing Next-Drupal’s role as a leading solution for modern headless Drupal architectures.

Next-Drupal offers a robust technical path to decouple your Drupal site without sacrificing the daily features that editors require. While Next-Drupal has numerous benefits, many decision-makers still question, "Why should I use a decoupled front-end when Drupal works fine?"

Over the past few weeks, we’ve been delving into the “We Are” phrases on our homepage. We’ve put a lot of thought into who we are as an agency and what words and phrases best describe us. We innovate within the Drupal space, we strategize on digital content, we lead by example, we offer expertise to our clients and the Drupal community, and we do great design work.

One of the great advantages of decoupled architecture is its ability to weather spikes in web traffic. With a traditional CMS, a sudden burst of traffic could overwhelm the server and paralyze your site, including the administration interface, which may only be used by a small fraction of your users. With a headless architecture, heavy traffic on the front-end can have little to no impact to the back-end.

At Chapter Three, we have a tight-knit team of experts in strategy, design, development, and project management. Our team members hold Drupal 9/10 developer and front-end certifications, demonstrating our technical expertise and commitment to staying at the forefront of web development best-practices.

In Part 1 of this series, we focused on innovation at Chapter Three. There was a lot to talk about there, from Next-Drupal and its various features, to the many original modules that Chapter Three developers have contributed to the Drupal universe. This post focuses on how we at Chapter Three are not only innovators, but also leaders.

Why do we call ourselves “Chapter Three”? It’s often said that in a novel, the real action doesn’t start until three chapters in, with the first two used to set up the characters and the scene. We like to think of ourselves as a place where the “real action” takes place, hence the name Chapter Three. It’s a name we landed on nearly two decades ago and one that still suits us.

The first DrupalCon of 2024 kicks off today and we are excited! Portland is always fun to visit, and this DrupalCon looks like a particularly good program, with topics ranging from Drupal 7 migration to AI integration to Drupal 11.

Happy March! If you’re reading this blog post on the day of publication, you now have exactly ten months to migrate out of Drupal 7 before it reaches end of life on January 5, 2025. After numerous extensions, this date is final and there will be no further extensions.

Remember Next-Drupal? It’s that thing we used to talk about incessantly but have been fairly quiet about in recent months. Not to worry – we haven’t lost interest. In fact, we’ve been working hard to make our Next.js-powered decoupled Drupal front-end product even better in Next-Drupal 2.0!

There’s a lot to be said for going decoupled with your website. From speed and scalability to increased security and front-end flexibility, headlessness offers solutions to most website shortcoming...

In November of 2021, Chapter Three unveiled Next-Drupal to the world as a new way for creating front ends for the Drupal CMS. Interest in this innovative decoupled solution has continually increased amid a growing headless market, the question of the best way to host a decoupled website is still evolving.

Next.js 13 uses special files for routing. Example route-name/page.tsx for building UI and route-name/loading.tsx for loading components. For page not found...

CSUB’s New Next.js Site Launches a New Era in Headless Performance California State University Bakersfield has an extensive continuing education program known as...

With Next-Drupal, we’re bringing the most popular front-end framework to your decoupled Drupal sites. In this talk, we go over what we are working on to make next-drupal ready for the fut...

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...

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:

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.

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...