Gatsby's Contentful demo

⚛️ 📄 🚀

Blazing fast modern site generator for React
Go beyond static sites: build blogs, e-commerce sites, full-blown apps, and more with Gatsby.

Have another more specific idea?
You may want to check out our vibrant collection of official and community-created starters.

👀 Live preview

https://gatsbydemocontentful.gatsbyjs.io/

🚀 Quick start

1. Clone this repo.

   Use your terminal to clone this repository.

   git clone https://github.com/gatsby-inc/gatsby-demo-contentful.git

2. Install dependencies.

   Navigate into your new site’s directory and install the dependencies.

   cd gatsby-contentful-demo
   npm install

3. Start developing.

   Start the development server.

   npm run develop

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

🚀 Quick start (Gatsby Cloud)

Deploy this demo with one click on Gatsby Cloud:

🧐 What's inside?

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

.
├── node_modules
├── src
├── .gitignore
├── .prettierrc
├── .prettierignore
├── gatsby-browser.js
├── gatsby-config.js
├── gatsby-node.js // tbc
├── gatsby-ssr.js // tbc
├── LICENSE
├── package-lock.json
├── package.json
├── postcss.config.js
├── README.md
└── tailwind.config.js

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. .prettierignore: This is a configuration file for Prettier and is set to ignore the .cache and public directories

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

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

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

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

10. LICENSE: This Gatsby demo is licensed under the 0BSD license. This means that you can see this file as a placeholder and replace it with your own license.

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

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

13. postcss.config.js: A JavaScript [PostCSS](https://postcss.org/ config file for TailwindCSS.

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

15. tailwind.config.js: A JavaScript config file for TailwindCSS.

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

💫 Deploy

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.