This starter is based on gatsby-starter-default. Kick off your project with this default boilerplate. This starter ships with the main Gatsby configuration files you might need to get up and running blazing fast with the blazing fast app generator for React.
Have another more specific idea? You may want to check out our vibrant collection of official and community-created starters.
- React.js 17 + Hooks - Blog introduce react v17.0.
- Gatsby.js 3 - Documentaion of gatsby.
- Typescript 4 - Documentation of typescript.
- Eslint 7 - Documentation of eslint.
- Prettier 2 - Documentation of prettier.
- Husky 5 - Documentation of husky.
- Lint Staged 10 - Documentation of lint staged.
- Gatsby Image - Documentation of gatsby plugins image for optimize image loading sites.
- Gatsby Offline - Documentation of gatsby plugins offline for PWA.
- Gatsby Manifest - Documentation of gatsby manifest for PWA.
- Gatsby React Helmet - Documentation of gatsby plugins react helmet for SEO.
- And other plugins gatsby default stater.
-
Create a Gatsby site.
Use the Gatsby CLI to create a new site, specifying the default starter. Noted: node >= 12.13.0
# create a new Gatsby site using the default starter gatsby new my-default-starter https://github.com/danangekal/gatsby-typescript-default-starter -
Start developing.
Navigate into your new site’s directory and start it up.
cd my-default-starter/ gatsby develop -
Open the source code and start editing!
Your site is now running at
http://localhost:8000!Note: You'll also see a second link:
http://localhost:8000/___graphql. This is a tool you can use to experiment with querying your data. Learn more about using this tool in the Gatsby tutorial.Open the
my-default-starterdirectory in your code editor of choice and editsrc/pages/index.tsx. Save your changes and the browser will update in real time!
A quick look at the top-level files and directories you'll see in a Gatsby project.
.
├── node_modules
├── src
├── .editorconfig
├── .eslintrc.json
├── .gitignore
├── .prettierrc.json
├── gatsby-browser.js
├── gatsby-config.js
├── gatsby-node.js
├── gatsby-ssr.js
├── LICENSE
├── package-lock.json
├── package.json
└── README.md
└── tsconfig.json
-
/node_modules: This directory contains all of the modules of code that your project depends on (npm packages) are automatically installed. -
/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.srcis a convention for “source code”. -
.editorconfig: This is a configuration file for editorconfig. EditorConfig is a file format and collection of text editor plugins for maintaining consistent coding styles between different editors and IDEs. -
.eslintrc.json: This is a configuration file for eslint. Eslint is a pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. -
.gitignore: This file tells git which files it should not track / not maintain a version history for. -
.prettierrc.json: This is a configuration file for Prettier. Prettier is a tool to help keep the formatting of your code consistent. -
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. -
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). -
gatsby-node.js: This file is where Gatsby expects to find any usage of the Gatsby Node APIs (if any). These allow customization/extension of default Gatsby settings affecting pieces of the site build process. -
gatsby-ssr.js: This file is where Gatsby expects to find any usage of the Gatsby server-side rendering APIs (if any). These allow customization of default Gatsby settings affecting server-side rendering. -
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: 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. -
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. -
tsconfig.json: This is a configuration file for typescript. The tsconfig. json file allows you to specify the root level files and the compiler options that requires to compile a TypeScript project.
Looking for more guidance? Full documentation for Gatsby lives on the website. Here are some places to start:
-
For most developers, we recommend starting with our in-depth tutorial for creating a site with Gatsby. It starts with zero assumptions about your level of ability and walks through every step of the process.
-
To dive straight into code samples, head to our documentation. In particular, check out the Guides, API Reference, and Advanced Tutorials sections in the sidebar.
Built with Gatsby - the blazing-fast static site generator for React.
