Frontend framework
Nuxt
The Vue meta-framework we use for full Vue sites and apps.
Nuxt is an open-source meta-framework built on Vue. It adds routing, server-side rendering, static generation and a project structure on top of Vue, roughly what Next.js is to React. HDC uses Nuxt when a whole site or app should live in the Vue ecosystem and needs to be server-rendered, so the content is fast, SEO-readable and built on a framework a Vue team can own.
Where it shines
- Server-side rendering and static generation give fast loads and SEO-readable HTML
- Hybrid rendering: pick prerendering, SSR, ISR or client-only per route
- File-based routing and a clear structure keep larger Vue projects organised
- Built on Vue, so it inherits Vue's approachability and Single-File Components
- Auto-imports and sensible defaults reduce boilerplate and setup time
- The natural choice when a whole site or app should live in the Vue ecosystem
Trade-offs to weigh
- Overkill for a simple marketing site, where a static Astro build is leaner
- Ships more JavaScript than a zero-JS static site by default
- Smaller ecosystem and hiring pool than the React/Next.js world in many markets
What Nuxt is
Nuxt is an open-source meta-framework built on Vue. Where Vue gives you the components and reactivity to build interfaces, Nuxt wraps a full framework around it: file-based routing, server-side rendering, static generation, data fetching, auto-imports and a clear project structure, all configured for you. In short, Nuxt is to Vue roughly what Next.js is to React, the step up from a UI library to a complete way of building and shipping whole sites and applications.
A defining strength is hybrid rendering. Nuxt lets you decide, route by route, how each page is produced: prerendered at build time, server-rendered on each request, revalidated on demand, or rendered only on the client. That flexibility means the public, SEO-critical pages can be static and fast while an interactive, app-like section behaves like real software, all in one codebase.
How HDC uses Nuxt
We treat Nuxt as the right tool for a particular situation: when a whole site or app should live in the Vue ecosystem and needs proper server rendering. The clearest case is a client whose team already builds in Vue and wants one coherent, maintainable codebase rather than a patchwork of technologies.
In those projects, Nuxt lets us:
- Prerender or server-render the marketing pages so they load fast and rank well.
- Build interactive, app-like sections that share the same Vue components and structure.
- Use hybrid rendering to pick the right strategy per route, balancing speed, freshness and SEO.
We pair Nuxt with TypeScript for type safety, Tailwind CSS for styling, and host and secure it through Cloudflare, the same disciplines we apply across the stack.
Why we apply it
The case for Nuxt is coherence and SEO in the Vue world. A plain client-side Vue app can be fast to develop but weak for search, because much of the content only appears after JavaScript runs. Nuxt fixes that by rendering on the server or at build time, so the content is in the HTML from the first byte, the same server-first principle that makes a site findable and quick.
For a client committed to Vue, Nuxt also means one consistent framework across the whole project, which keeps the codebase tidy and the long-term maintenance straightforward for their team.
How Nuxt fits our stack
Nuxt is the meta-framework we reach for when a project belongs wholly in the Vue ecosystem, the Vue-world counterpart to Next.js in the React world. It sits above Vue’s components, adding routing and rendering, with TypeScript for safety and Tailwind CSS for styling layered on as usual, hosted and secured on Cloudflare. Within our wider toolkit it occupies the same niche as Next.js: where Astro handles fast content and marketing sites, Nuxt handles fuller Vue sites and app-like builds that need server rendering and structure.
When Nuxt isn’t the right tool
We’re honest about fit, and for most of our clients that means not using Nuxt. For a standard marketing or trades website, Nuxt is more framework than the job needs, a static Astro build is leaner, cheaper to host and just as SEO-friendly, while shipping far less JavaScript. Nuxt earns its place when a project is genuinely part of the Vue ecosystem and needs server rendering across a whole site or app. If a client isn’t committed to Vue, or the project is a simple content site, we’ll build on Astro instead and explain why.
Worked example
A full site and tool built in the Vue ecosystem
Picture a regional firm whose team already builds in Vue and wants their whole public site plus a customer-facing tool built in one consistent ecosystem they can maintain. Rather than mixing technologies, we'd build it on Nuxt: the marketing pages prerendered or server-rendered so they load fast and rank well, and the interactive tool sharing the same Vue components and project structure. Nuxt's hybrid rendering lets us choose, route by route, whether a page is static, server-rendered or revalidated on demand, so the public pages stay SEO-friendly while the app behaves like real software. The client gets one coherent codebase their Vue developers are comfortable owning. (Illustrative, every build is scoped to your goals.)
Better together
How Nuxt fits with the rest of our stack
Nuxt: your questions answered
What is Nuxt used for?
Nuxt is used to build full Vue sites and applications with server-side rendering or static generation. It adds routing, rendering, project structure and sensible defaults on top of Vue, so a whole site or app can be built in one organised codebase rather than wired together by hand.
Why does HDC use Nuxt?
We use Nuxt when a whole project should live in the Vue ecosystem and needs to be server-rendered for speed and SEO. If a client's team builds in Vue, Nuxt lets us deliver a complete, fast, search-friendly site or app on a framework they can maintain. For a standard marketing site, we'd usually build on Astro instead, because a static site is leaner there.
What's the difference between Nuxt and Next.js?
They're the same idea in two different ecosystems. Next.js is the meta-framework for React; Nuxt is the meta-framework for Vue. Both add routing, server-side rendering, static generation and structure on top of their underlying library. We choose between them based on whether a project belongs in the Vue world or the React world.
What's the difference between Nuxt and Vue?
Vue is the core framework for building components and interfaces. Nuxt is built on top of Vue and adds everything you need to ship a whole site or app: routing, server rendering, static generation and project structure. We use Vue for interactive pieces and Nuxt when the entire project should be a Vue application.
Is Nuxt good for SEO?
Yes, because Nuxt can render pages on the server or prerender them at build time, so the full content is in the HTML for search engines and AI crawlers to read. That makes it far stronger for SEO than a plain client-side Vue app. For a pure marketing site, a static Astro build is still leaner, which is why we reserve Nuxt for fuller Vue projects.
Should I build my marketing site on Nuxt?
Usually only if you're already committed to the Vue ecosystem. For most trades and local-business marketing sites, a static Astro build is faster, cheaper to host and just as SEO-friendly. Nuxt makes the most sense when a site is part of a larger Vue project or genuinely app-like. We'll always advise honestly on which fits your case.
Want Nuxt working for your business?
Tell us what you're trying to achieve, we'll show you, honestly, whether it's the right tool and how we'd apply it.
Enquire now