
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 that generates HTML on the server rather than relying on the browser to render the initial page from JavaScript. When a user requests a page, the server renders the initial HTML and sends it to the client. This can improve performance and SEO by making meaningful page content available earlier to users and easier for search engines to crawl and index.
Below you will find a subset of articles from my blog specifically about Server‑Side Rendering as well as how it relates to JavaScript SEO rendering and indexing. This is a topic I have worked with for many years, although it has not been one I have written about often. There are six articles collected here so far, 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.