Buy Now and unlock this series
$
49
.99
yours forever
$
49
.99
Become a Pro and unlock everything
$
24
.99
per month
$
24
.99
Netlify & Github
Now that we have our project started, we're ultimately going to want to deploy it somewhere. We'll create a new repository with GitHub and integrate with Netlify to create a new deployment pipeline for a Next.js app that will allow us to easily push new changes to the web.
Downloads
Become a pro to download code and videos
Ecommerce on the Jamstack with Snipcart, Next.js, & WordPress
16 videos
Released: July 31 2021
Course Instructor
Colby Fayock
- Introduction
1m30s - NextJS
8m14s - Netlify & Github
15m46s - Sass, Components, Store Header
21m33s - Products, CSS Grid, Button component
22m39s - Snipcart, Env Variables
17m16s - WordPress, WPGraphQL
18m53s - GraphQL, Apollo Client
14m4s - Autodeploy with Web Hooks
5m50s - Dynamic Routes
19m27s - Custom Snipcart Hook
16m39s - Shared Layout
8m22s - Branding & Personality
23m26s - Snipcart Theming & Customization
24m13s - Custom Taxonomy
23m17s - Search
16m50s
Comments
Linda
5 months ago
No wonder I was struggling to get next.js projects onto Github, this is the first time I hear that I am meant to skip the first steps that Github gives me. Worked a charm. thanks a mil Colby :)
Ev
9 months ago
A noob question, is the serverless target necessary if deploying to Vercel?
Raul
11 months ago
@Adam Yeah, you should add it if you want to use the serverless target.
Adam
11 months ago
I did not need to add the target:serverless to my next.config.js - everything deployed without issue and is live. Should I add it any way for future proofing?
Want to join the conversation?
Become a Pro member today!