Buy Now and unlock this series
$
44
.99
$
34
.99
yours forever
$
44
.99
$
34
.99
Become a Pro and unlock everything
$
24
.99
per month
$
24
.99
Building Our Static SIte
Here, we are going to be talking about the build process for Gatsby and how we can deploy it. We are going to start by using the Gatsby build tool and begin the process of getting things up in running so we can create our static Gatsby site and experience the unique benefits that building a site with Gatsby offers.
Downloads
Become a pro to download code and videos
Pro Gatsby 2
26 videos
Course Instructor
Scott Tolinski
- Pro Gatsby
40S - Getting Started With GatsbyJS
8M10S - Gatsby FIles Explained
12M22S - Creating Pages
9M29S - Working With Assets
7M50S - Intro To GraphQL
7M59S - GraphQL Static Queries
8M6S - Plugins & Gatsby Source Filesystem
9M27S - Working With Markdown
16M27S - Our Query In React
12M17S - Improving Our Query with Filtering and Sorting
11M3S - Gatsby Node
11M16S - Creating Pages From Markdown Files
9M1S - Page Query vs Static Query
8M45S - Context In Page Queries
6M3S - Static Query From Scratch & Page Listing
12M35S - Styled Components In Gatsby
14M44S - Styling Part 2
9M3S - Gatsby Image
13M19S - React Spring
12M16S - Building Our Static SIte
7M20S - Hosting On Netlify
8M18S - Netlify CMS
9M50S - Easy Sitemaps
5M30S - Progressive Web Apps With Gatsby
5M44S - Where To Go Next
4M18S
Comments
Zac
almost 3 years ago
I was able to fix the pathname error by passing "location" through from the remaining pages like 404, the team page, and the second blog post page. It's not because it isn't available when building, it's because it wasn't always being passed through. If you scrolled up a little bit, it would tell you which page needed to pass location through. Defaulting the prop is really just hiding the actual problem.
Want to join the conversation?
Become a Pro member today!