Vue/Nuxt hands-on tutorial: from zero to your first runnable project
Step-by-step walkthrough of Vue/Nuxt with copy-paste commands, directory layout, and a first runnable artifact.
On this page
Quick answer
Which preset do I use to static-render Nuxt?
Use nitro preset:static or nuxt generate. SSR / CSR behavior differs across Nuxt majors — validate hydration before upgrading.
Machine-readable page data: /data/vue-tutorial.json
In-depth analysis
Nuxt is Vue's meta-framework, hybrid by default with first-class static generation. nuxt generate or nitro preset:static produces pure static HTML, ideal for edge distribution. Going from zero to a first runnable project is about locking in the smallest end-to-end loop before you scale.
// nuxt.config.ts — full-site static generation
export default defineNuxtConfig({
ssr: true,
nitro: { preset: 'static' },
});
// Build: nuxi generateVue/Nuxt Hands-on Tutorial · Key takeaways
- Project initialized with the official scaffold
- Dependencies pinned to a single pnpm lockfile
- Local dev server starts and first paint is reachable
- First runnable commit pushed
FAQ & pitfalls
Why does my Nuxt client hydration fail?
Usually mismatched SSR vs CSR environment variables. Unify the runtime variable source to keep server and client rendering aligned.
Explore the hub
See all 5 guides in Vue & NuxtSame category as this article, sorted across the codebase.
Vue/Nuxt architecture: layered patterns for high-concurrency edge apps
The edge-delivery view of Vue/Nuxt's layering and data flow.
Vue/Nuxt best practices: engineering conventions for production
Field-tested Vue/Nuxt practices from production, avoiding the common anti-patterns.
Vue/Nuxt deployment guide: zero-ops edge publishing with Cloudflare Pages
Git-driven Vue/Nuxt deployment in practice: commit to build, atomic publish to every edge node.
Vue/Nuxt performance tuning: push first paint and edge response to the limit
Around Vue/Nuxt's real bottlenecks, an actionable LCP / INP / CLS checklist.
Share & save
What readers are asking
Questions that keep coming back in reader feedback, already answered.
- 01
Why is my Astro component's interactivity not working?
Components ship as zero-JS HTML by default, so an interactive one needs a client:* directive (client:load, client:visible, …). Without it the script is never bundled into the page.
See the full guide → - 02
Why is my custom Tailwind v4 brand colour not applied?
Colours must be declared in @theme (for example --color-brand). A missing @tailwindcss/vite plugin, or a leftover v3 config, makes bg-brand silently render nothing.
See the full guide → - 03
Why are _headers / _redirects not taking effect?
Both files must sit at the root of the output directory (dist/); anything under src/ is never uploaded. A purely static project should not add _worker.js either — that gives up the zero-cold-start advantage.
See the full guide →