[{"data":1,"prerenderedAt":14},["ShallowReactive",2],{"blog-post-building-for-static-today-and-ssr-tomorrow":3},{"slug":4,"title":5,"description":6,"category":7,"publishedAt":8,"readingTime":9,"content":10},"building-for-static-today-and-ssr-tomorrow","Building for Static Today and SSR Tomorrow","How to keep a Nuxt project lean for SSG now without blocking hybrid rendering later.","Architecture","2026-04-10","4 min read",[11,12,13],"A future-proof Nuxt codebase keeps rendering concerns close to the framework and business logic separate from page components. That means page files stay focused on composition and presentation while data loading lives in composables or APIs.","For static generation, prerendering known routes is enough. When the product evolves, the same composables can call server routes or external APIs without forcing a full rewrite of the page layer.","Route rules give you an explicit map for where static delivery is enough and where authenticated or personalized flows can switch to SSR later.",1776859604129]