Gatsby's Hello-World Starer -> Blog Website

PROJECT SUMMARY

This repo contains code for a blogging website utilizing GatsbyJS.
The website follows Andrew Mead's GatbsyJS Bootcamp: https://www.youtube.com/watch?v=8t0vNu2fCCM
The starter code shipped with the main Gatsby configuration files you might need to get up and running blazing fast with the blazing fast app generator for React.

LIVE DEMO OF WEBSITE

Users can can look through the website that was deployed from this repo:
https://angry-bassi-7e8f67.netlify.com/

Built With

• GatsbyJS
• GraphQL
• Contentful
• Netlify
  check package-lock and gatsby-node.js files for other dependencies/plugins

Prerequisites

To install Gatsby and Node.js, it is recommended to use Homebrew. A little set-up in the beginning can save you from some headaches later on!
Visit https://www.gatsbyjs.org/tutorial/part-zero/ for a development environment tutorial straight from Gatsby's website

• Node
• NPM
• Git
• Gatsby CLI

Fork/Clone/Download

File configurations

1. Create a .env file outside of your folders
2. Create an account with Contentful and Netfliy with your Github credentials.
   • Contentful (https://www.contentful.com/)
   • Netlify (https://www.netlify.com/)
3. In your .env file, insert the following: (this is needed to connect to the Contentful data)

• GATSBY_GRAPHQL_IDE=playground (this is to use the playground version of GraphQL)
• CONTENTFUL_SPACE_ID=yourCredentials
• CONTENFUL_ACCESS_TOKEN=yourCredentials

Get Started!

1. In a terminal, type 'npm install' to get all of the dependencies into your local repo.

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

cd gatsby
in your terminal run `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)

Completed features listed below

• Able to switch between navigation tabs seamlessly
• Responsive design
• Integrate with Contentful's Content Management System
  • Able to upload blogs that contain title, date, body, images, and more
• Contains useful resources in blogs to learn about GatsbyJS

Next Steps

• Redesign the front end to create a more personal style > tutorial's design
• Have more appealing styles, possibly add animations
• Add more blogs to share resources about GatsbyJS
• Try integrating GatsbyJS with other CMS

🧐 What's inside?

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

.
├── node_modules
├── src
├── .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. .gitignore: This file tells git which files it should not track / not maintain a version history for.

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

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

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

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

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

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

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

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

12. 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, Gatsby recommend starting with their 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 Gatsby documentation. In particular, check out the Guides, API Reference, and Advanced Tutorials sections in the sidebar.

gatsby