Engineering
Why Nuxt is our default web framework
The reasons Nuxt is our standard choice for web products, and the circumstances in which we recommend an alternative.
1 min read
We are technology-agnostic in principle but deliberate in practice. For the majority of the web products we deliver, Nuxt is our default framework, and the reasons are practical rather than fashionable.
Rendering and performance
Server-side rendering and static generation are built in, which addresses search visibility and first-load performance from the outset. File-based routing and auto-imports keep teams productive without unnecessary configuration.
A unified backend
Nitro, the server engine behind Nuxt, allows a lightweight backend to sit alongside the front end. This removes an entire category of integration code and simplifies deployment.
When we recommend an alternative
- Next.js — when the client's team works primarily in React, or plans to share components with a React Native mobile app.
- Astro — when a site consists almost entirely of static content.
The framework is never the objective. The objective is the most direct route to a fast, maintainable product.