Nuxt.
Nuxt is an application framework built on Vue that adds file-based routing, server-side rendering, static generation and a server layer. It exists to answer the questions a plain Vue application leaves open — rendering strategy, data fetching, deployment target — with conventions rather than configuration.
Where Nuxt fits on a long engagement.
The decision that matters on a Nuxt project is the rendering strategy, and it is usually made in week one by whoever scaffolded the repository. Static generation, server rendering and client-only rendering have very different consequences for search visibility, hosting cost and how fresh data can be, and moving between them later touches far more code than the config flag suggests.
Nuxt's server layer is the part teams most often underuse or overuse. It is genuinely useful for a thin API-shaping layer close to the frontend; it becomes a problem when business logic migrates into it and the application ends up with two backends that disagree about the rules.
What an assigned team does with Nuxt.
Because the rendering strategy is expensive to revisit, it is worth deciding with the people who will live with it rather than inheriting it from a template. On a standing assignment that decision is revisited deliberately when the product changes shape, instead of becoming a constraint nobody remembers choosing.
Nuxt work frequently sits on the boundary between a marketing surface and an application surface, which makes it one of the places where design and engineering capacity have to be scoped together rather than sequentially, usually under an outsourced design team alongside the frontend specialists.
What we use Nuxt for.
- Products where search visibility is revenue Server-rendered or statically generated pages that crawlers get fully formed rather than as an empty shell.
- One stack across marketing and application A content surface and a logged-in surface sharing components, so the brand does not diverge between them.
- Revisiting a rendering strategy chosen too early Moving specific routes between static, server and client rendering as the data freshness requirements become clear.
How Nuxt capacity is assigned.
Nuxt capacity is assigned under software development outsourcing, with the rendering strategy treated as an architectural decision at scoping rather than a default inherited from a starter template.
Tell us what your roadmap needs Nuxt for.
A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.
Loading the contact form… You can also email hello@azendo.co.
We reply within one working day. No obligation, and no newsletter.