Before touching Gatsby, you need to master HTML, CSS, JavaScript ES6+, React basics, and the concepts of static site generation and JAMstack. In this episode you'll also set up Node.js LTS, an editor, and the Gatsby CLI to kick off your journey.

Welcome to the Learn Gatsby series! This series will take you through mastering Gatsby — a React framework for building ultra-fast, SEO-friendly, production-ready static sites — from foundational concepts all the way to deployment. There are 24 episodes in total, organized into six phases.
Before writing your first line of code, there are a few core skills and software you need to have. Why do these prerequisites matter? Because Gatsby is built on React and uses GraphQL as its data layer. If you've never seen JSX or don't understand build-time rendering yet, almost every upcoming episode will feel confusing.
Episode 0 is your roadmap: we'll confirm your baseline skills, set up Node.js LTS, an editor, and the Gatsby CLI, then verify the entire toolchain before moving on to episode 1.
Gatsby produces HTML, CSS, and JavaScript. You should be comfortable with semantic markup, flexbox and grid for layout, and modern JavaScript features like const, let, arrow functions, destructuring, the spread operator, and module imports. Without this foundation, component code will be hard to read.
Gatsby is built on React. What you need to know: functional components, props, state with useState, effects with useEffect, conditional rendering, and mapping lists of data into elements. Gatsby 5 uses React 18, so also understand hydration — the process of bringing static markup back to life as an interactive application in the browser.
Gatsby is a static site generator (SSG) and follows the JAMstack pattern: JavaScript, APIs, and Markup. Pages are built at build time into static HTML files, then served through a CDN. You'll need to understand the difference between SSG, SSR (server-side rendering), and CSR (client-side rendering), because this entire series uses those terms.
Gatsby 5 requires Node.js version 18 or higher. The safest approach is to use the latest LTS version via nvm so it's easy to switch versions:
nvm install --lts
nvm use --ltsVerify that Node.js and npm are installed correctly:
node --version
npm --versionThe commands node --version and npm --version should print version numbers. Make sure the Node version is at least 18; if it's still 16, update it first because Gatsby 5 doesn't support it.
VS Code is the most popular editor for Gatsby development. Install extensions that speed up your workflow: ES7+ React/Redux/React-Native snippets for JSX, Prettier for automatic formatting, and GraphQL for syntax highlighting of queries in code files. Other editors like JetBrains WebStorm also work, but this series assumes VS Code.
Use a modern browser such as Chrome, Firefox, or Edge for development. Open DevTools to inspect the network, performance, and console. For hardware, Gatsby needs at least 8GB of RAM because the build process loads the entire data graph into memory; the single-threaded Node.js process will work hard when building hundreds of pages.
The Gatsby CLI is the main tool throughout this series: creating projects, running the dev server, and building production bundles. Install it globally:
npm install -g gatsby-cliWhen it's done, verify it:
gatsby --versionThe command gatsby --version prints the CLI version. If you don't want to install it globally, use npx gatsby --version to run the CLI without a permanent install.
Info
The CLI version and the Gatsby version inside your project can differ. The CLI is thin — most of the logic actually lives in the gatsby dependency inside your project. Episode 3 covers this structure in depth.
Also set up Git for version control and a GitHub account to host your repository. In episodes 19-20 we'll connect a Gatsby project to CI/CD. Verify Git:
git --versionBefore moving on to episode 1, run a quick verification to make sure everything is ready:
node --version
npm --version
gatsby --version
git --versionThe output of all four commands should print versions without errors. If any of them fails, stop and fix it first — a solid foundation will make the next 23 episodes much easier.
In episode 0 you've laid the groundwork for the entire series: understanding the core skills of HTML, CSS, JavaScript ES6+, React, and the SSG/JAMstack concepts, and then setting up Node.js LTS, VS Code, and the Gatsby CLI.
Key takeaways:
In the next episode we'll cover the history, background, and why you need Gatsby — from Gatsby's birth as a static site generator, the evolution of versions 1 through 5, to the performance and SEO problems it solves. Make sure your toolchain is ready, because the Learn Gatsby journey is just beginning!