Simple pet-project generated using gatsby-starter-hello-world starter
-
Back-end link to Contentful with Hooks to Netlify
- Gatsby 3.0
- Quick Start
- Gatsby Starters
- Hello world starter
- Gatsby Plugin Library
- gatsby-plugin-styled-components
- Normalize.css
- Figma Logo Creator Plugin
- React Icons Package
- React Icons npm
- Responsive Images
- Free Stock Photos
- gatsby-plugin-image
- Gatsby Config API
- gatsby-source-filesystem
- Using the Gatsby Image plugin
- gatsby-source-contentful
- Environment Variables
- File System Route API
- slugify npm package
- Gatsby Node APIs
- gatsby-plugin-webfonts
- React Helmet
- gatsby-plugin-react-helmet
- Importing and exporting content with the Contentful CLI
Requirements:
- Node.js
- Contenful - add items (images, title, description)
- Formspree - contact form backend service
- Netlify - deploy project
- Favicon
npm i
npm i -g gatsby-cli
gatsby --version
npm install -g npm@7.10.0
gatsby new gatsby-starter-hello-world https://github.com/gatsbyjs/gatsby-starter-hello-world
gatsby clean
gatsby develop
Open Contentful
- create space
- go to => Content model => create content type:
- go to => Content => add new item
- go to => Media => add new image
query {
site {
info: siteMetadata {
title
description
author
person {
name
age
}
simpleData
complexData {
name
age
}
}
}
}
-
- JSON => copy/paste to Contentful content JSON object
- Markdown
- MDX
- Manually
- Programmatically using Setting up in Gatsby-Node.js - tags pages template: tag-template.js & gatsby-node.js is an old way how to create pages
- Programmatically using Filesystem route API - recipes pages template: {ContentfulRecipe.title}.js
cd pages
create file: {ContentfulRecipe.title}.js
cd src
create file: template/tag-template.js
cd /
create file: gatsby-node.js
- Content model - structure for a data
- Content types fields
- rich text
- text (title, description)
- number (cookTime, servings, prepTime)
- date & time
- location
- media (image)
- boolean (featured)
- JSON objects (content)
- reference
- Add Webhook (Menu => Settings)
- Login
- Menu => Sites
- Drag and drop your site output folder here
gatsby clean && gatsby build
- drag & drop
public
folder
- New site from Git
- Create a new site
- Connect to Git provider
- Pick a repository
- Show Advanced Build Settings => New Variable =>
CONTENTFUL_API_KEY=h7a9U5luZ**********
- Site settings, and deploy!
- Build & Deploy => Build Hooks => Add build hook =>
https://api.netlify.com/build_hooks/608da*******
=> copy / paste to Contentful => Settings => Webhooks => save (Netlify will restart the build after making some changes in Contentful)
- Drag and drop your site output folder here
Kick off your project with this hello-world 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.
-
Create a Gatsby site.
Use the Gatsby CLI to create a new site, specifying the hello-world starter.
# create a new Gatsby site using the hello-world starter gatsby new my-hello-world-starter https://github.com/gatsbyjs/gatsby-starter-hello-world
-
Start developing.
Navigate into your new siteβs directory and start it up.
cd my-hello-world-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-hello-world-starter
directory in your code editor of choice and editsrc/pages/index.js
. 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
βββ .gitignore
βββ .prettierrc
βββ gatsby-browser.js
βββ gatsby-config.js
βββ gatsby-node.js
βββ gatsby-ssr.js
βββ LICENSE
βββ package-lock.json
βββ package.json
βββ README.md
-
/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.src
is a convention for βsource codeβ. -
.gitignore
: This file tells git which files it should not track / not maintain a version history for. -
.prettierrc
: 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
(Seepackage.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.
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.
Build, Deploy, and Host On The Only Cloud Built For Gatsby
Gatsby Cloud is an end-to-end cloud platform specifically built for the Gatsby framework that combines a modern developer experience with an optimized, global edge network.