Repository files navigation

• Features
• Web Performance Tests
• Quick Start
• Deploy with Netlify
• Folder Structure
• License

• Accessible
• Fast
• Built as part of100 Days of Gatsby Challenge 2021. Live site is athttps://rodneylab100daysofgatsbymain.gtsb.io/home.

• Lighthouse Report - Scores 100 on Performance, Accessibility and Best Practices. Hosting on Gatsby Cloud Free, ax-robots-tag: none header is served. This causes the SEO score to drop from 100 to 91.

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

# Create a new Gatsby site using this repogatsby new blog https://github.com/rodneylab/rodneylab-100-days-of-gatsby

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

cd bloggatsby develop

Your site is now running athttp://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 theGatsby tutorial.

Open theblog directory in your code editor of choice and editsrc/templates/index-template.js. Save your changes and the browser will update in real time!

Gatsby Cloud is a platform of stable, trusted tools launched by the team behind Gatsby.js. Seeinstrcutions on setting up a Gatsby Cloud deploy.

Netlify CMS can run in any frontend web environment, but the quickest way to try it out is by running it on a pre-configured starter site with Netlify. Use the button below to build and deploy your own copy of the repository:

After clicking that button, you’ll authenticate with GitHub and choose a repository name. Netlify will then automatically create a repository in your GitHub account with a copy of the files from the template. Next, it will build and deploy the new site on Netlify, bringing you to the site dashboard when the build is complete. Next, you’ll need to set up Netlify’s Identity service to authorize users to log in to the CMS.

To deploy to github pages, simply do the following:

• Ensure that yourpackage.json file correctly reflects where this repo lives
• Change thepathPrefix in yourconfig.js
• Run the standard deploy command

yarn deploy

$ git clone https://github.com/[GITHUB_USERNAME]/[REPO_NAME].git$ cd [REPO_NAME]$ yarn$ yarn develop

To test the CMS locally, you'll need run a production build of the site:

$ yarn build$ gatsby serve

└── src    ├── components    │   ├── Emoji    │   ├── Footer    │   ├── Header    │   ├── Layout    │   └── PageHeader    ├── constants    ├── pages    ├── templates    └── utils