When my team picks a front-end framework for a new build, we start with React. We’ve shipped work in Vue with Nuxt, Angular, Svelte, and Node with Express, and React keeps winning for three reasons. WordPress and Drupal both run React inside their editors. More developers use React than any other front-end framework, which gives our clients more options for who maintains their site. And Next.js, which sits on top of React, covers the speed and search needs of a public website. Some sites are better off without it, and I’ll cover those at the end.
We’ve shipped work in Vue, Angular, Node, and React
Vue with Nuxt is the pairing we’ve used most. Angular shows up in past client work, Svelte in internal experiments, and Node with Express on the back end. Each one was a sound choice for the project in front of us at the time.
Working across all of them taught me that a framework choice outlasts the project. The client lives with it for years, hiring around it, updating it, and extending it. When I weigh a framework against that, React comes out on top.
Calculators, configurators, and internal tools show where the framework matters
A brochure page doesn’t ask much of a framework. An interactive tool asks a lot. The page has to respond as someone answers a question or changes a number, keep track of their choices, and give them a result they can trust.
A lot of our JavaScript work looks like this:
- For a national insurance agency, we created an interactive questionnaire that walks visitors through their insurance options.
- For K8ssandra, the open source distribution of Apache Cassandra for Kubernetes, we created a configurator. Users pick their settings in the browser and download a configuration file to use in their own instances.
- For Virginia Credit Union (VACU), we created several custom calculators to VACU’s specifications. They run on VACU’s own rates, which gives members accurate models of their options.
We also run COLAB on software we wrote. Our team has built at least a dozen internal applications, including production quality, client experience, sales, and proposal tools, plus performance auditors. They pull information from the systems we use to run the business and turn it into something we can act on.
React’s component model fits this work. A question, an input, or a result becomes its own piece that the next developer can read, test, and change without breaking the rest of the tool.
WordPress and Drupal both put React inside the editor
Much of our work is in WordPress, and the WordPress block editor is a React application. Each block in the editor is a React component, including the custom blocks my team builds for client sites. Our WordPress work and our application work run on one skill set.
Drupal has moved the same way. Drupal Canvas, the visual page builder released as 1.0 in December 2025, lets front-end developers build components in React without learning Drupal first.
Here’s why I care about that overlap. A component pattern we build for a WordPress site can inform a Drupal or Next.js project, and a developer who maintains one can read the others. Fewer specialized skills stand between your team and a change to your site.
More React developers means less dependence on one agency
In Stack Overflow’s 2026 Developer Survey, 41.5% of respondents reported using React. Vue was at 17.2%, Angular at 16.0%, and Svelte at 7.8%.
That gap matters when you’re the one keeping the site running. On React, you can hire an in-house developer, bring in a contractor for a busy season, or move to another agency without rebuilding. I want our clients able to run and extend what we build without us, and picking a framework with a big developer pool is one of the ways we do that.
Next.js adds what public websites need on top of React
Next.js is a framework built on React that handles the parts of a public website React leaves open: page routing, server rendering, static generation, and image optimization. Visitors get a finished page that loads quickly, and search engines and AI assistants can read the content without running any code first. Vercel’s research found that none of the major AI crawlers render JavaScript.
React on its own usually renders the page in the visitor’s browser. That’s fine for tools behind a login, like a member portal or an internal dashboard. Public pages are different. A patient looking for a provider, a member comparing loan rates, or a donor reading about a program is often on a phone, sometimes on a slow connection, and usually coming from a search result. Next.js sends them a finished page first and adds interactivity after.
The React team now recommends starting new sites with a framework, and Next.js is the first one it lists. Routing, caching, and image handling come standard. Fewer of those decisions are one-off choices for a single project, and that makes the code easier for the next developer to pick up.
Headless Drupal with a Next.js front end
We’re close to launching a site for a cultural heritage organization that pairs Drupal and Next.js. Drupal manages the content, with structured content types, editorial roles, and revision history the client’s staff use to publish. Next.js renders the public site visitors see.
I like this split, often called headless or decoupled, because each system does the job it’s suited to. Drupal is a strong content repository for organizations with structured, connected content, like stories tied to places, people, and dates. Next.js handles speed and the visitor experience.
We’re also testing where Next.js fits on other sites we support, including a new offering whose content management system is itself built on Next.js. I’m making a bet that this approach will serve more of our clients, and we’ll adjust as we learn.
When we recommend something other than Next.js
Headless adds moving parts, and I want you to see them before you choose it. A Drupal and Next.js site is two applications to host, update, and secure. Editor preview takes setup work, because the page an editor sees in the CMS isn’t the page the visitor sees by default. Next.js also needs hosting that can run server code, through a platform like Vercel or Netlify or a Node server.
For a nonprofit with a small communications team and a straightforward content site, a well-built WordPress site is often the better call (we compare the two in WordPress vs. Drupal). React still powers the blocks, and there’s one system to maintain. We make that call based on who runs the site after launch, how often it changes, and what it needs to connect to.
Talk with us about your next build
If you’re weighing a rebuild, a move to headless, or a custom tool for your members, patients, or donors, I’d love to hear what you’re working on. Which part of your site does your team struggle to change today? See more of our development work, or let’s talk.
