Best Practices for Managing Environment Variables in Next.js
Best practices for managing environment variables in Next.js, so secrets stay server‑side and deployments do not freeze the wrong values at build time.
Articles
Node.js
Node.js is a cross‑platform, open‑source JavaScript runtime outside the browser. The interesting part is not that front‑end engineers can avoid another language; it is that the same language can support servers and build tooling whilst taking on a very different set of runtime responsibilities.
Best Practices for Managing Environment Variables in Next.js. 
The Execution Context in JavaScript. The Execution Context in JavaScript
Execution context defines how JavaScript code runs, from global scope to function calls. Here, I explore how it works in browsers, React, Next.js, and Node.js.
Redirect a Default Vercel Subdomain to Your Custom Domain. Redirect a Default Vercel Subdomain to Your Custom Domain
When you set up a custom domain in Vercel, the default
vercel.appsubdomain still serves your site, which can lead to duplicate content. Here's how to fix it.
Vue 3 Reactivity: Proxies vs. Vue 2 Reactivity. Vue 3 Reactivity: Proxies vs. Vue 2 Reactivity
Vue 3 replaces Vue 2's getters and setters with JavaScript proxies. This article explains how they differ and why proxies improve Vue's reactivity system.
Using Next.js Proxy for Route Protection. Using Next.js Proxy for Route Protection
Protect Next.js routes with Proxy, formerly Middleware, using authentication, authorisation, matchers, API request checks and current terminology.
Implementing Authentication in Next.js Using NextAuth.js. Implementing Authentication in Next.js Using NextAuth.js
A practical guide to implementing authentication in Next.js with NextAuth.js, including sessions, callbacks, route protection, and router‑specific trade‑offs.
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.
Resolving mini-css-extract-plugin Warnings in Gatsby. Resolving
mini-css-extract-pluginWarnings in GatsbySeeing Conflicting Order warnings in your Terminal whilst building your Gatsby project is not uncommon, but fortunately is very easy to fix (or suppress) too.
Gatsby & GraphQL: Nodes vs. Edges. Gatsby & GraphQL: Nodes vs. Edges
Gatsby and GraphQL nodes versus edges explained through graph theory, query shape, pagination, and why Gatsby data often exposes both structures.
Automatically Submit Sitemaps to Google During Gatsby Build. Automatically Submit Sitemaps to Google During Gatsby Build
A historical Gatsby sitemap‑ping workflow, with a postscript explaining Google's retired endpoint and how to keep sitemaps discoverable.
Static Site Generators. Static Site Generators
Static site generators trade runtime complexity for build‑time output. This article looks at the benefits, the drawbacks, and where they fit best.
ReferenceError: Window is Not Defined in Gatsby. ReferenceError: Window is 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.
Installing Gatsby onto an M1 MacBook Air. Installing Gatsby onto an M1 MacBook Air
Set up Gatsby on an M1 MacBook Air with Xcode, Homebrew, nvm, Node.js, vips, Yarn, the Gatsby CLI, dependency reinstall steps, and native image dependencies.
Disabling Gatsby Telemetry. Disabling Gatsby Telemetry
Disable Gatsby telemetry cleanly, with context on what anonymous analytics collect, why teams opt out, and how the setting affects local and CI work.
Replace Inline Styles in Gatsby with an External CSS File. Replace Inline Styles in Gatsby with an External CSS File
Replace Gatsby's inlined production CSS with an external stylesheet by rewriting headComponents, with performance trade‑offs and historical context.
Disabling Source Maps in Gatsby for Production. Disabling Source Maps in Gatsby for Production
Disable production source maps in Gatsby with webpack, understand external versus inline maps, and clear old map files without changing development builds.
Adding Static Files to a Gatsby Site. Adding Static Files to a Gatsby Site
Add static files to a Gatsby site using the static folder, with notes on build output, verification files, legacy assets, and when not to process files.
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.