Skip to content

Latest commit

 

History

History
133 lines (87 loc) · 7.08 KB

README.md

File metadata and controls

133 lines (87 loc) · 7.08 KB
Raw

Gatsby Kentico Kontent

Boilerplatev Gatsby Kontent Starter

Kick off your project with this boilerplate which is based on BoilerplateV style. 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.

🚀 Quick start

  1. Create a Gatsby site.

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

    # create a new Gatsby site using the default starter
gatsby new my-boilerplatev-starter https://github.com/viperfx07/gatsby-starter-boilerplatev-kontent

  2. Start developing.

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

    Note: on Windows machine, please make sure the drive letter in the path is in capital letter.

    cd my-boilerplatev-starter/
yarn dev

    yarn dev or yarn d will run gatsby develop.

  3. 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-boilerplatev-starter directory in your code editor of choice and edit src/pages/index.js. Save your changes and the browser will update in real time!

🧐 What's inside?

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

.
├── node_modules
├── src
├── .babelrc
├── .editorconfig
├── .eslintrc.js
├── .gitignore
├── .prettierrc
├── gatsby-browser.js
├── gatsby-config.js
├── gatsby-node.js
├── gatsby-ssr.js
├── LICENSE
├── package-lock.json
├── package.json
└── README.md

  1. /node_modules: This directory contains all of the modules of code that your project depends on (npm packages) are automatically installed.

  2. /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”.

  3. .babelrc: This is a configuration file for Babel. It has @babel/plugin-proposal-nullish-coalescing-operator and @babel/plugin-proposal-optional-chaining pre-installed on this starter

  4. .editorconfig: This file will ensure the code editor uses the same styling. If you're using Visual Studio Code, please install EditorConfig for VS Code

  5. .eslintrc.js: This is a configuration file for ESLint

  6. .gitignore: This file tells git which files it should not track / not maintain a version history for.

  7. .prettierrc: This is a configuration file for Prettier. Prettier is a tool to help keep the formatting of your code consistent.

  8. 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.

  9. 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).

  10. 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.

  11. 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.

  12. jsconfig.json: This file is telling the code editor i.e. Visual Studio Code that indicates that the directory is the root of a JavaScript Project. Also, any aliases used such as @ or @@ can be picked up by the editor to resolve the path

  13. LICENSE: Gatsby is licensed under the MIT license.

  14. yarn.lock (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).

  15. package.json: A manifest file for Node.js projects, which includes things like metadata (the project’s name, author, etc). This manifest is how Yarn knows which packages to install for your project.

  16. README.md: A text file containing useful reference information about your project.

🎓 Learning Gatsby

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.

🐛 Known issues

  • Multiple "root" queries found in file

    This happens most likely on Windows machine. This issue has been reported on Github (here). To fix it, you need to make sure the drive you change to in the Command Prompt, is in capital letter. e.g.

    cd C:\dev\my-boilerplatev-starter

  • Running gatsby develop produces an error "Cannot find module 'webpack/package.json"

    This issue has been reported on Github here. To fix it, Add a resolutions in package.json to enforce svg-sprite-loader version to 4.1.3

    {
	"resolutions": {
		"svg-sprite-loader": "4.3.1"
	}
}

💫 Deploy

Deploy to Netlify