Insights that inspire

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.

What is the difference between a goal, an objective, a strategy, and a tactic? Simply put, a goal is the desired end result, an objective is a nearer-term benchmark in the direction of your goal, a strategy is the path toward your objective, and a tactic is a single element of your strategy.

Design is the lifeblood of what we do at Chapter Three. While much of this blog is devoted to development-related topics like decoupled Drupal, all development revolves around the design that supports it. Design is what clients and audiences see and engage with, and it makes or breaks a website as much as the site’s infrastructure.

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.

The saying “content is king”, a cliche at this point, hearkens to an essay written by Bill Gates in 1996 about the future of the Internet, in which he predicted that “those who succeed will propel the Internet forward as a marketplace of ideas, experiences, and products—a marketplace of content.”

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.