
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 (SSR) is a web development technique which generates HTML pages ‑ usually composed in JavaScript ‑ on the server rather than client‑side (in the browser). In response to a user request, the server compiles the HTML, and sends a fully‑rendered page to the client. This improves performance and SEO by ensuring content is quickly accessible and easily indexed by search engines.
Below you will find a subset of articles from my blog specifically about Server‑Side Rendering. Although this is a topic I've been working with for many years, it's fair to say that I've not written about it often. I've only managed to publish six articles about it, which you can see and read below.

How to implement server‑side rendering in Vue, with a clearer mental model for hydration, data loading, caching, and where SSR actually pays off.

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.

Add seeded randomisation to an SSR Gatsby project, keeping content order deterministic across builds while still rotating destination‑style content.
Fix 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`GetStaticProps` vs. `getServerSideProps` in Next.js explained with build‑time and request‑time data fetching, trade‑offs, and practical page examples.

Compare static generation and server‑side rendering in Next.js through freshness, request‑time data, performance, SEO, operational cost, and page intent.