GitHub - gatsbyjs/gatsby-starter-blog-theme: Starter for using the official gatsby blog theme

Quickly get started using the Gatsby blog theme! This starter creates a new Gatsby site that is preconfigured to work with the official Gatsby blog theme.

To get started, check out the guide to using the Gatsby blog theme starter , or the longer, more detailed tutorial .

Navigate into your new site’s directory and start it up.

Use the Gatsby CLI to create a new site, specifying the blog theme starter.

Deploy this starter with one click on Gatsby Cloud:

Here are the top-level files and directories you’ll see in a site created using the blog theme starter:

/content: A content folder holding assets that the theme expects to exist. This will vary from theme to theme — this starter is set up to get you started with the blog theme, which expects an image asset for your avatar, and blog post content. Replace the avatar image file, delete the demo posts, and add your own!
/src: You will probably want to customize your site to personalize it. The files under /src/gatsby-theme-blog shadow, or override, the files of the same name in the gatsby-theme-blog package. To learn more about this, check out the guide to getting started with using the blog theme starter.
.gitignore: This file tells git which files it should not track / not maintain a version history for.
.prettierrc: This file tells Prettier which configuration it should use to lint files.
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. When using themes, it’s where you’ll include the theme plugin, and any customization options the theme provides.
LICENSE: This Gatsby starter is licensed under the 0BSD license. This means that you can see this file as a placeholder and replace it with your own license.
package-lock.json (See package.json below, first). This is an automatically generated file based on the exact versions of your npm dependencies that were installed for your project. (You won’t change this file directly).
package.json: A manifest file for Node.js projects, which includes things like metadata (the project’s name, author, etc). This manifest is how npm knows which packages to install for your project.
README.md: A text file containing useful reference information about your project.