Migrate to Netlify Today

Netlify announces the next evolution of Gatsby Cloud. Learn more

Modifying a Starter

While a Gatsby starter is a working website out of the box, chances are you’ll want to modify your starter at some point. Building on top of a starter reduces the amount of boilerplate code you need to write yourself. You’re therefore able to write your own content, functionality, and styling faster.


What you need to know will depend on the starter you choose and the data or functionality you’d like to modify. Even if you choose not to modify the starter’s components, you may still want to update text, use data from an external source, and modify the style (CSS) of the site. To do this, you’ll write some Markdown and JSON.

To modify the functionality of a starter, you’ll want a basic understanding of JSX syntax for updating components and making new ones. You’ll also want some knowledge of GraphQL for querying your data. Start with these and add to your skills as you continue to add functionality to your starter.

Choosing a starter

To choose a starter, first consider the functionality you need. Are you building an e-commerce site? A blog? Do you already know what data sources you’ll want to use? Find a starter that fulfills your requirements by using the searchbar and filters in the Gatsby Starter Library.

If you’re not sure what to choose or want only the most essential functionality, try customizing either gatsby-starter-blog (if you’re primarily using this site as a blog) or gatsby-starter-default. These official starters are maintained by Gatsby and are great options, particularly for your first Gatsby site.

Exploring the folder structure

Taking the default Gatsby starter as an example, dedicate some time to looking through some of the most important files in the repository (repo). You’ll find most of these in the root (or main) folder of your project. Doing so will give you a clearer picture of how the various parts of your Gatsby site work together.

Default starter file structure in VS Code

  • src/pages: a directory for page components to live, with at least one index.js file (example).
  • gatsby-config.js: a space to add configurable data and plugins. Among the API files, gatsby-config.js is the one you’re most likely to need to modify. See Gatsby Config for more information.
  • package.json: the “command center” for Gatsby dependencies and scripts. Find an example in the default starter’s package.json file.
  • README.md: this should include instructions for how to install and configure the starter, a list of its features or structure, and helpful tips. If you plan to share the source code for your site with other people, you can replace this information with documentation for your specific project.
  • static: a directory for static assets, such as a favicon.ico file. You can add whatever static files you need in here and they’ll be copied to the public folder. If you’re not sure which files belong here, check out the How-To Guide about the static folder.

If you’d like to read descriptions of all of these files, as well as the other files that make up a Gatsby site, check out the Gatsby project structure documentation.

Adding content

How exactly you add content to your site will depend somewhat on your starter’s structure. The default starter includes the src/pages/ directory, which contains 404.js, index.js, and page-2.js. Adding a JavaScript file to this directory will automatically create a new route available at http://localhost:8000/[file-name]. For example, if you’d like to add a page to share your speaking experience, you might include speaking.js in src/pages/ as written below:

At this point, you can navigate to http://localhost:8000/speaking in your browser to view this page! You can also add pages from Markdown or source data from a content management system (CMS) like WordPress. You may even choose a specific starter because it’s built to work well with a certain CMS. Try explicitly searching the Gatsby Starter Library for your preferred system. Once there, check out the category filter. You’ll see several options prefixed with “CMS:“. Choose the option(s) that best fit your goals for the project.

Querying data

Being able to query your own data will provide an added level of customization and control over your site. By default, Gatsby does this using GraphQL. Note the siteMetadata in the default starter’s gatsby-config.js:

Elsewhere on the site, GraphQL queries access that data and display it in the browser. The Layout component, for instance, runs a query for siteMetadata’s title property. It then passes that value to the Header component via props:

This allows the Header to set the content of the <h1> that appears on every page of the website to the value of siteTitle:

Try adding a property to siteMetadata, querying for it, and displaying the data on a page of your site. The Gatsby docs have a great introduction to querying your data with GraphQL.

Customizing styles

Continuing with gatsby-starter-default as an example, have a look at src/pages/index.js:

Here, some inline styles are being applied to a <div> element. This option will work but may become difficult to manage over time as your styles become more complex. You may wish to use another of several available styling methods. Gatsby doesn’t have an opinion about which styling approach you choose.

You may even choose a specific starter because of its approach to styling. Search the Gatsby Starter Library using category filters prefixed with “Styling:” and choose the option(s) that best fit your project.

Starter Library with Styling: SCSS filter selected

Other resources

Start building today on Netlify!
Edit this page on GitHub
© 2023 Gatsby, Inc.