This is a starter storefront to use for your project’s design system. A storefront is a single source of truth for a system. It’s where any adopter (designers, developers, etc) can access the processes, documentation, and tooling needed for using the system.

Demo Site

Table of Contents

🧐 What’s inside?

A quick look at the top-level files and directories you’ll see in this Gatsby project.

.
├── content
├── node_modules
├── src
├── .gitignore
├── .prettierrc
├── gatsby-browser.js
├── gatsby-config.js
├── gatsby-node.js
├── LICENSE
├── package-lock.json
├── package.json
└── README.md
  1. /content: This directory contains all of the markdown files and assets for the site.
  2. /node_modules: This directory contains all of the modules of code that your project depends on (npm packages) are automatically installed.
  3. /src: This directory will contain all of the code related to what you will see on the front-end of your site (what you see in the browser) such as your site header or a page template. src is a convention for “source code”.
  4. .gitignore: This file tells git which files it should not track / not maintain a version history for.
  5. .prettierrc: This is a configuration file for Prettier. Prettier is a tool to help keep the formatting of your code consistent.
  6. gatsby-browser.js: This file is where Gatsby expects to find any usage of the Gatsby browser APIs (if any). These allow customization/extension of default Gatsby settings affecting the browser.
  7. gatsby-config.js: This is the main configuration file for a Gatsby site. This is where you can specify information about your site (metadata) like the site title and description, which Gatsby plugins you’d like to include, etc. (Check out the config docs for more detail).