Keeping Gatsby Builds Predictable
Keep Gatsby builds predictable by controlling data sources, plugins, image work, environment variables, cache assumptions, and build‑time dependencies.
Articles
Static Sites, page 2 of 2
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‑nine articles collected together for you below.
Keeping Gatsby Builds Predictable. 
Automatically Deploy a Static Gatsby Site via FTP. Automatically Deploy a Static Gatsby Site via FTP
Deploy a static Gatsby build over FTP with environment variables, ftp‑deploy, build scripts, and a practical CI flow for conventional or legacy hosting.
Understanding getStaticPaths in Next.js. Understanding
getStaticPathsin Next.js`GetStaticPaths` in Next.js explained with dynamic routes, pre‑rendered paths, fallback behaviour, and how static generation works for slug‑based pages.
Using getStaticProps with CMS Data. Using
getStaticPropswith CMS DataUse getStaticProps with CMS data without hiding freshness, build‑time, preview and validation risks in Pages Router content workflows.
GetStaticProps vs. getServerSideProps in Next.js. getStaticPropsvs.getServerSidePropsin Next.js`GetStaticProps` vs. `getServerSideProps` in Next.js explained with build‑time and request‑time data fetching, trade‑offs, and practical page examples.
Static Generation with CMS Content and Build‑Time Data. Static Generation with CMS Content and Build‑Time Data
How static generation works with CMS content and build‑time data, including routes, previews, rebuilds, freshness, cache limits, and deployment trade‑offs.
What is a Static Site Generator? What is a Static Site Generator?
Static site generators explained in plain English, including how they compare with SSR, ISR and modern framework rendering choices.
Deploying Static Front Ends with Netlify and Build Hooks. Deploying Static Front Ends with Netlify and Build Hooks
How Netlify build hooks deploy static front ends from CMS updates, scheduled changes, content edits, preview needs, and simple publishing workflows.
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.
Redirect a Default Netlify Subdomain to Your Custom Domain. Redirect a Default Netlify Subdomain to Your Custom Domain
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.
Prepending PHP to a Page in Gatsby. Prepending PHP to a Page in Gatsby
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.