[{"data":1,"prerenderedAt":37},["ShallowReactive",2],{"blog-posts":3},[4,15,26],{"slug":5,"title":6,"description":7,"category":8,"publishedAt":9,"readingTime":10,"content":11},"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",[12,13,14],"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.",{"slug":16,"title":17,"description":18,"category":19,"publishedAt":20,"readingTime":21,"content":22},"designing-reusable-ui-with-tailwind-and-vue","Designing Reusable UI with Tailwind and Vue","A practical approach to reusable components that stay flexible as product requirements change.","Design System","2026-04-06","5 min read",[23,24,25],"Reusable components do not need a large design system upfront. A small set of primitives such as buttons, cards, navigation shells, and spacing conventions cover most early product needs.","Tailwind works best when utility classes express layout and visual intent directly in the component, while extracted component classes handle repeated shell patterns.","The main goal is consistency without rigidity, so teams can move quickly and still keep the interface cohesive.",{"slug":27,"title":28,"description":29,"category":30,"publishedAt":31,"readingTime":32,"content":33},"mock-data-strategies-that-scale-into-real-apis","Mock Data Strategies That Scale into Real APIs","Why composable-driven data access makes the transition from local content to remote APIs straightforward.","Data","2026-04-01","3 min read",[34,35,36],"Using static in-repo data during the first delivery phase reduces moving parts and keeps deployments simple. The mistake is wiring that data directly into every page.","A thin data-access composable creates a stable interface for fetching lists and detail records. Today it can return local arrays, and later it can call useFetch or a server route.","That separation keeps UI code steady while the delivery model changes underneath it.",1776859604129]