NX-01
Nuxt 3 Applications
Greenfield Nuxt 3 builds — SSR, Nitro server routes, composables, auto-imports, and hybrid rendering per route.
Nuxt 3NitroComposition API
Sheet · Nuxt
Technology · Nuxt Development
Nuxt 3, shipped properly.
Nuxt 3 applications with SSR, Nitro, hybrid rendering, and edge deployment. The Vue ecosystem at production scale.
Sheet 01 · Overview
The Vue meta-framework, used the way it was designed.
Nuxt 3 is one of the better Vue stories of the last few years — Nitro on the server, composables on the client, auto-imports cleaning up boilerplate, hybrid rendering letting you mix SSR, ISR, and static per route.
We have shipped Nuxt projects across marketing sites, dashboards, commerce storefronts, and internal tools — usually paired with Pinia for state, Tailwind for styling, and DigitalOcean or Vercel for hosting.
When you want the SEO and performance of a server-rendered framework without leaving the Vue ecosystem, Nuxt 3 is hard to beat. We are built on it.
Sheet 02 · Schedule of Capabilities
Capabilities delivered.
6 core areas
Scoped per brief
Scoped per brief
NX-02
Nuxt 2 → 3 Migration
Legacy Nuxt 2 codebases migrated to Nuxt 3 — module by module, composable by composable, with feature flags during cutover.
MigrationNuxt 2
NX-03
Hybrid Rendering
SSR for dynamic routes, ISR for cacheable content, static for marketing pages — all in one build.
SSRISRStatic
NX-04
State & Data
Pinia for app state, useFetch and useAsyncData for SSR-safe data, custom composables for cross-component logic.
PiniauseFetchComposables
NX-05
Modules & Plugins
Custom Nuxt modules for cross-cutting concerns. Server middleware, plugin injection, and runtime config configured per environment.
ModulesPlugins
NX-06
Performance
Image optimization, payload extraction, route-based splitting, and edge rendering — Lighthouse 95+ as the target.
PerformanceCWV
Sheet 03 · Process
How we build with Nuxt.
- Phase 01
Architecture
Pages, layouts, composables, server routes, and rendering strategy mapped before code begins.
- Phase 02
Build
Components first, then pages, then server routes. Auto-imports keep the surface tight. Pinia stores added only when truly app-wide.
- Phase 03
Deploy
Nitro builds for Node, Edge, or static. CI configured with type checking, linting, and preview environments per branch.
- Phase 04
Operate
Retained development on the Nuxt codebase — module evolution, feature work, and minor version upgrades shipped continuously.
Sheet 04 · Stack
Tools we reach for.
Nuxt 3Vue 3NitroPiniaTypeScriptTailwind CSSNuxt ContentNuxt Image@nuxt/iconVueUseVitest@vue/test-utilsGitLab CIDigitalOcean App Platform
Sheet 05 · FAQ
Questions, answered.
Why Nuxt over Next or Remix?
Nuxt is the right pick when the surrounding stack is Vue, when SEO and SSR are first-class, or when the team prefers Vue's ergonomics. Next for React stacks, Remix for tight server-form workflows, Nuxt for everything in between when Vue is the choice.
Are you using Nuxt 3?
Yes — Nuxt 3 is the default. Nitro server, composables, auto-imports, hybrid rendering. We migrate legacy Nuxt 2 projects to Nuxt 3 when the codebase supports it.
How does Nuxt handle SEO and Core Web Vitals?
SSR or hybrid rendering, payload extraction, route-based code splitting, image optimization via Nuxt Image, and structured data via useHead. CWV-friendly out of the box; we tune for Lighthouse 95+ scores routinely.
Can you migrate from Nuxt 2 to Nuxt 3?
Yes. The migration is non-trivial — composables, plugins, modules, and TypeScript shifts are all different. We scope the migration to a written plan based on a codebase audit.
What about state management?
Pinia is the Nuxt 3 standard. We use it for app-wide state; route-local state stays in composables. Vuex only when maintaining legacy code.
Sheet 07 · Start a brief
Build it in Nuxt.
Tell us what the application is and what the rendering needs are. We'll come back with a Nuxt 3 architecture.