
Understanding getStaticPaths in Next.js
`GetStaticPaths` in Next.js explained with dynamic routes, pre‑rendered paths, fallback behaviour, and how static generation works for slug‑based pages.
Articles
Static sites are websites where pages are generated ahead of the request, usually during a build or publishing workflow. The articles in this category cover static generation with CMS content, build hooks, Gatsby, Next.js, Netlify, and the operational trade‑offs that appear when a supposedly simple static site starts depending on live editorial data.
Below you will find a subset of articles from my blog specifically about Static Sites. This is an area I have worked with for many years, and it has been a regular subject in my writing. There are twenty‑seven articles collected together for you below.

getStaticPaths in Next.js`GetStaticPaths` in Next.js explained with dynamic routes, pre‑rendered paths, fallback behaviour, and how static generation works for slug‑based pages.

getStaticProps with CMS DataUse Next.js getStaticProps with CMS data by fetching entries, validating fields, handling slugs, previews, rebuild behaviour, fallbacks, and errors.

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.

How static generation works with CMS content and build‑time data, including routes, previews, rebuilds, freshness, cache limits, and deployment trade‑offs.

Static site generation has continued to grow and grow in popularity. I try and explain what one is, and why it might be suitable to you or your project.

How Netlify build hooks deploy static front ends from CMS updates, scheduled changes, content edits, preview needs, and simple publishing workflows.

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

When you set up a custom domain in Netlify, the default `netlify.com` subdomain still returns your app, which can lead to duplicate content. It is an easy fix.

Need a little PHP inside a Gatsby build? This guide shows a pragmatic way to prepend server‑side code when a fully static approach is not enough.