brittani1128 / gatsby-intro

Frontend Masters: Introduction to Gatsby

In this course, learn to build blazing fast apps and websites with React using Gatsby, a static PWA (Progressive Web App) generator. Over 50% of people will abandon a mobile site if it takes more than 3 seconds to load. Unless you’re willing to give up half of your potential customers, performance is no longer optional on the modern web. Fortunately, there are a lot of tools available to help you build screaming fast websites. Unfortunately, there’s a frighteningly large number of performance considerations, and many of them are easy to get wrong.

What You’ll Learn

• Learn how to leverage free, open source tools including Gatsby, React, and GraphQL to build high-performance websites.
• Deliver an excellent experience to your users by providing only critical assets on load and prefetching assets for subsequent page loads.
• Implement performance best practices, such as the PRPL pattern, lazy loading assets, and more.
• Learn to build and deploy blazing fast websites in the fraction of time.
• Create websites quickly with performance baked in.
• Deploy your sites for free in minutes with Netlify.

A Note About Running the Code

We recommend getting the code running on your computer to build your confidence working with Gatsby. If you get stuck, use the Course Errata below to debug, or refer to the the step branches to see what is different between your code and the reference code.

Course Code Running on CodeSandbox

You can jump into the CodeSandbox for each branch without having to get the code running on your computer. Keep in mind, that if you want to modify the code, you'll need to create a CodeSandbox free account to fork a new sandbox and save it to your CodeSandbox account.

• Course Starter
• Step 0: Pages & Links
• Step 1: Styles
• Step 2: GraphQL & SEO
• Step 3: MDX
• Step 4: MDX Blog
• Step 5: Hero Image
• Step 6: Blog Images
• Step 7: Source Plugins with Instagram Datasource
• Step 8: Analyze Bundle (must fork to run npm run analyze)

Getting Course Code Running on Your Machine

For windows users, go through the installation instructions for cross-env and add it to your package.json develop script.

1. npm install
2. npm run develop
3. Open http://localhost:8000/

Course Slides (hit the right/down arrow keys to progress through the slides)

Refer to the Course Errata below if you are running into issues.

Prerequisites

1. Have a text editor installed, i.e. VSCode
2. Have the Gatsby CLI (gatsby-cli) installed globally by running: npm install -g gatsby-cli

Course Errata

Video: Rendering Components in MDX video at 1 minute, 32 seconds where Jason installs the Gatsby MDX plugin.

The gatsby-mdx plugin was deprecated in favor of gatsby-plugin-mdx.

Fixed code: See this commit to migrate to gatsby-plugin-mdx

npm install gatsby-plugin-mdx instead of gatsby-mdx

View the step4/mdx-blog branch for final code for the section.

Video: Adding Optimized Images to Post at 1 minute, 49 seconds where Jason configures remark images.

An additional config line needs to be added to configure gatsby-remark-images.

Fixed code: See this commit to configure gatsby-remark-images'

    {
      resolve: 'gatsby-plugin-mdx',
      options: {
        defaultLayouts: {
          default: require.resolve('./src/components/layout.js'),
        },
        gatsbyRemarkPlugins: ['gatsby-remark-images'],
        plugins: ['gatsby-remark-images'],
      },
    },

View the step6/blog-images branch for final code for the section.

Video: Getting Post by Slug at 4 minutes, 55 seconds where Jason gets the post body.

gatsby-plugin-mdx no longer requires body to be nested in code in the query

in post.js the query should be

export const query = graphql`
  query($slug: String!) {
    mdx(frontmatter: { slug: { eq: $slug } }) {
      frontmatter {
        title
        author
      }
      body
    }
  }
`

Instead of

export const query = graphql`
  query($slug: String!) {
    mdx(frontmatter: { slug: { eq: $slug } }) {
      frontmatter {
        title
        author
      }
      code {
        body
      }
    }
  }

More details in issue #27