Ways to architecture your vue/nuxt app
summary
Compares Vue and Nuxt with concrete tradeoffs: Nuxt automatic routing and SSR for SEO and PWA and using Vuex modules to isolate contexts like cart; contrasts three concrete patterns — components fetching themselves, page-as-data-gatekeeper, and container-level stores — with real e‑commerce pain points and which patterns scale or break. Describes migrating a project to Nuxt, when containers reduce prop drilling, and practical rules: align UI to component architecture and document APIs for maintainability.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:47Geisy Domiciano (Jay-Z)
- 1:31What is Vue.js and Nuxt.js?
- 6:42Each component mind its business
- 8:59Page owns the information
- 10:15Page fetches, page child manipulates
- 13:19Page and containers deals with data
- 18:15Take aways
related talks
38mLarge Scale Nuxt Architecture
34mNuxt + Vue: The Game-Changer Your New Projects Deserve
37mPatterns for Large Scale Vue.js Applications
27mUniversal Vue applications with Nuxt.js
29mSpeed up your Vue js development time with Nuxt.js
44mNuxt.js - Why? How? Oh yeah!
55mNuxt.js: isomorphic Vue.js Apps made easy, fast and fun
22mDeep dive into Nuxt.js