Implementing Server‑Side Rendering (SSR) in Vue
How to implement server‑side rendering in Vue, with a clearer mental model for hydration, data loading, caching, and where SSR actually pays off.
Articles
Server‑Side Rendering
Server‑side rendering (SSR) moves the first useful HTML response back to the server, but that does not make it the right answer for every route. These articles look at the boundary between server output and browser hydration, including what the choice means for performance and SEO when compared with static generation.
Implementing Server‑Side Rendering (SSR) in Vue. 
Access Search Parameters in Next.js SSR'd Layout. Access Search Parameters in Next.js SSR'd Layout
Whilst replatforming an app, I came across this limitation in Next.js: you cannot (easily) access search parameters in an SSR layout. Here, I share my solution.
Introducing Seeded Randomisation into an SSR Gatsby Project. Introducing Seeded Randomisation into an SSR Gatsby Project
Add seeded randomisation to an SSR Gatsby project, keeping content order deterministic across builds whilst still rotating destination‑style content.
ReferenceError: window is Not Defined in Gatsby. ReferenceError:windowis Not Defined in GatsbyFix window is not defined in Gatsby or Next.js by understanding SSR, guarding browser globals, lifecycle timing, dynamic imports, and third‑party modules.
getStaticProps vs. getServerSideProps in Next.js. getStaticPropsvs.getServerSidePropsin Next.jsgetStaticPropsvs.getServerSidePropsin Next.js explained with build‑time and request‑time data fetching, trade‑offs, and practical page examples.
Static Generation vs. Server‑Side Rendering in Next.js. Static Generation vs. Server‑Side Rendering in Next.js
Compare static generation and server‑side rendering in Next.js through freshness, request‑time data, performance, SEO, operational cost, and page intent.