Headless Shopify starter built on Next.js π€
Headless CMS powered by Sanity.io β‘
Features β’ Tours β’ Set Up β’ Spin Up β’ Deployment β’ Extras
- Utility-first CSS with Tailwind CSS
- Animations powered by Framer Motion
- Cart powered by Shopify Buy SDK
- Real-time inventory check for products using SWR
- Customizable Filtering & Sorting for product collections
- Klaviyo waitlist form for out-of-stock products
- Klaviyo newsletter form with opt-in field
- Dynamic Page Routes for custom page creation
- Automatic
Sitemap.xml
generation - Automatic
robots.txt
generation - Automatic 301 Redirects from Sanity
- Live Preview content directly from Sanity
- Modern Image component using Sanity's Hotspot, Crop, and automatic WEBP format
- Modular page content for all pages, including dynamic grid layouts
- Customizable Promotion Banner
- Customizable Cookie Notice
- Accessibility features:
- ARIA Landmark Roles
- Default focus states preserved for keyboard navigation
- Correctly trap focus for drawers with focus-trap-react
- Roving tabindex for radio buttons
- Input-based quantity counters
- Required
alt
text for all images - "Skip to Content" link
- SEO features:
- Page-level SEO/Share settings with previews
- Fallback Global SEO/Share settings
- Automatic JSON-LD Schema markup for products
- Automatically syncs products from Shopify into Sanity
- Custom action to sync product cart thumbnails back to Shopify from Sanity
- Tracks product status (draft/published) from Shopify to help control visibility while editing
- Deleted products and variants are preserved and flagged in Sanity
- Updates the URL on variant changes while keeping a clean history stack
- Vanity shop URL masking
- Global Cart with access to all variant data for line items
- Supports Single Variant products out of the box
- Product photo galleries with variant granularity
- Dynamic
/shop
collection page - Custom collection pages
- Ability to surface a variant option on product cards
Still not sold? Here's some videos to get you psyched:
Famous 5-Minute Setupβ’ - Coming Soon
From sync to sale, watch me spin up a fresh storefront in under 5 minutes!
Explore the file Structure - Coming Soon
In-depth look at the file structure, naming conventions, and logic under the hood
Setting up your first Product - Coming Soon
Explore the Product settings within Sanity and how to properly setup PDP pages and PLP cards
Connecting to Klaviyo and testing your Forms - Coming Soon
Learn how to quickly connect Klaviyo to utilize product waitlist and newsletter forms
Setup your first Vercel deployment - Coming Soon
Using the Sanity Vercel Deploy plugin, see how easy it is to empower your clients to trigger deploys
Quickly deploy as a Sanity Starter on Vercel with a pre-populated store! Once deployed, simply follow step 2 and 3 below to connect your Shopify store.
β οΈ Important!
Existing products will not automatically sync into Sanity.
You will need to trigger this by making a change to your product(s) in Shopify.
Clone this repository from your GitHub account with the Use this template button
- If you don't have the Sanity CLI installed, first run
npm install -g @sanity/cli
to install it globally npm install && sanity init
in the/studio
folder- During Sanity's initalization it will warn you, type
Y
and hitenter
:
? The current folder contains a configured Sanity studio. Would you like to reconfigure it? (Y/n)
- When it asks you what dataset configuration to use, go with the
default
- Add CORS Origins to your newly created Sanity project (visit: manage.sanity.io and go to Settings > API): - Add your Studio URLs with credentials:
http://localhost:3333
and[subdomain].sanity.studio
- Add your front-end URLs without credentials:http://localhost:3000
andhttps://[subdomain].vercel.app
β οΈ Important!
For "singleton" documents, like settings sections, the schema uses a combination of__experimental_actions
and the new actions resolver. If you are using this outside of the official Sanity Starter, you will need to comment out the__experimental_actions
line in "singleton" schemas to publish settings for the first time. This is because a singleton is still a document type, and one needs to exist first before it can be edited. Additionally, if you want to create additional "singleton" schemas, be sure to edit thesingletons
array in the following file:/studio/parts/resolve-actions.js
.
- Enable Private Apps in Shopify
- Apps > "Manage Private Apps" (text link in page footer)
- Enable Private Apps
- Create new Private App
- Apps > Manage Private Apps > "Create private app"
- Give this a relevant name, I prefer: "Headless Storefront", so it's clear what it's being used for
- Use your dev email to know when there are issues
- Change Admin API permissions on "Products" to
Read and write
- Allow this app to access your storefront data using the Storefront API, with at least the following permissions:
- Read inventory of products and their variants
- Read and modify checkouts
- Go to "Settings" (bottom left) -> "Notifications" -> "Webhooks" (very bottom)
- add the following webhooks:
- product creation -
[your-domain]/api/shopify/product-update
- product update -
[your-domain]/api/shopify/product-update
- product deletion -
[your-domain]/api/shopify/product-delete
β οΈ Note
You have to use a real domain name (no localhost). Be sure to use your Vercel project URL during development, and then switch to the production domain once live. You may not know your Vercel project URL until you deploy, feel free to enter something temporary, but make sure to update this once deployed!
npm install
in the project root folder on local- Create an
.env.local
file in the project folder, and add the following variables:
SANITY_PROJECT_DATASET=production
SANITY_PROJECT_ID=XXXXXX
SANITY_API_TOKEN=XXXXXX
SHOPIFY_STORE_ID=XXXXXX
SHOPIFY_API_TOKEN=XXXXXX
SHOPIFY_API_PASSWORD=XXXXXX
SHOPIFY_WEBHOOK_INTEGRITY=XXXXXX
// Needed for Klaviyo forms:
KLAVIYO_API_KEY=XXXXXX
// Needed for Mailchimp forms:
MAILCHIMP_API_KEY=XXXXXX-usX
MAILCHIMP_SERVER=usX
// Needed for SendGrid forms:
SENDGRID_API_KEY=XXXXXX
- Update all the
XXXXXX
values, here's where to find each:
SANITY_PROJECT_ID
- You can grab this after you've initalized Sanity, either from thestudio/sanity.json
file, or from your Sanity Manage dashboardSANITY_API_TOKEN
- Generate an API token for your Sanity project. Access your project from the Sanity Manage dashboard, and navigate to: "Settings" -> "API" -> "Add New Token" button. Make sure you giveread + write
access!SHOPIFY_STORE_ID
- This is your Shopify store ID, it's the subdomain behind.myshopify.com
SHOPIFY_API_TOKEN
- Copy the Storefront Access Token you copied from setting up your Private Shopify App. (Note: This is not the Admin API Key, scroll to the bottom where it says "Storefront API" for the correct value)SHOPIFY_API_PASSWORD
- Copy the Admin API password from "Apps" -> "Manage private apps" -> [your_private_app].SHOPIFY_WEBHOOK_INTEGRITY
- Copy the Integrity hash from "Settings" -> "Notifications" -> "Webhooks" (very bottom of page)KLAVIYO_API_KEY
- Create a Private API Key from your Klaviyo Account "Settings" -> "API Keys"MAILCHIMP_API_KEY
- Create an API key from "Account -> "Extras" -> API KeysMAILCHIMP_SERVER
- This is the server your account is from. It's in the URL when logged in and at the end of your API KeySENDGRID_API_KEY
- Create an API key from "Settings" -> "API Keys" with "Restricted Access" to only "Mail Send"
Since we're serving our store through a headless environment, we don't want visitors accessing our unused shopify theme. The domain for this is visible during checkout, and is publicly accessible. To silence it, replace your current theme's theme.liquid
file with the one from this repo, and replace YOUR_STOREFRONT_DOMAIN_NO_PROTOCOL
with your actual frontsite domain URL (do not include protocol or trailing slash)
This will essentially "pass-through" URLs accessed at your Shopify Store to your true headless storefront (ie. shop.hull.dev/products
-> hull.dev/products
)
npm run dev
in the project folder to start the front end locally
- Your front end should be running on http://localhost:3000
sanity start
in the /studio
folder to start the studio locally
- Your Sanity Studio should be running on http://localhost:3333
β οΈ Gotcha!
If you did not manually set up your project, theprojectId
in/studio/sanity.json
will still be set to the HULL demo project. Make sure to update this before starting the studio, otherwise you will be denied access when trying to access your studio.
This is setup to work seamlessly with Vercel, which I highly recommend as your hosting provider of choice. Simply follow the on-screen instructions to setup your new project, and be sure to add the same .env.local
variables to your Vercel Project
This is an easy one, you can simply run sanity deploy
from the /studio
folder in your project. Select a subdomain you want; your Studio is now accessible from the web. This is where I'll invite the client to manage the project so they can both add billing info and begin editing content.
Once you hand off to the client you'll want to give them the ability to generate builds when they make updates within the Sanity Studio. The easiest way to do this is through my Vercel Deploy plugin.
This looks like a theme... How can I use this like a starter?
While this starter is relatively opinionated, the goal was three-fold:
- Use high-quality packages that don't get in the way
- Solve common UX problems and complex logic so you can focus on the fun stuff
- Create a more approachable starter for anyone looking to build production-ready headless Shopify experiences
That being said, I understand this means a lot of what's included is very opinionated. However, you'll find that at it's core the structure and naming conventions lend itself to really making it your own.
I've purposefully used extracted component classes, not only for cleaner file structure, but also so you can easily work in your own styles exclusively within the styles folder. Feel free to extend or outright remove the applied styles for all of the components!
What's up with the CSS? Why are you using @apply?
Previously, @apply
was used to extract component classes away from your javascript files. However, since then Tailwind has been opposed to this approach. In the coming releases HULL will move away from this approach in favor of applying styles directly to the components so functionality and styling is done in one place.
You can read more about Tailwind's stance on @apply
here: https://tailwindcss.com/docs/reusing-styles#avoiding-premature-abstraction
Can I use this for non-Shopify projects?
Absolutely! This starter was actually born out of a non-shopify starter I had been using for my own client projects.
I made a marketing-starter
branch that is HULL without all the Shopify logic! The fastest way to get started is simply cloning that branch locally into an empty project folder:
git clone -b marketing-starter --single-branch [email protected]:ndimatteo/HULL.git .
You can read the setup instructions for this version from the branch's README.
Error: Failed to communicate with the Sanity API
If you get this error in your CLI, you need to logout and log back in again. Simply do sanity logout
and then sanity login
to fix.
Access your "product_sync" metafields in Shopify without using a plugin
Simply navigate directly to: https://[store_id].myshopify.com/admin/bulk?resource_name=Product&edit=metafields.sanity.product_sync
(making sure to replace [store_id]
with your Shopify Store ID)
How do I properly hand-off a Vercel project to the client?
While not as easy as Netlify, what I prefer to do is:
- Have the client create their own Vercel account
- At the time of writing, Github connections can only be connected to one Vercel account at a time, so have the client create a Github account if they don't already have one, and transfer the project repo to them
- Delete the dev project from your own Vercel account (this is so the client can utilize the project name and domain you were using during dev)
- You or the client can now connect their newly transferred Github repo to their own Vercel account!
How can I see the bundle size of my website?
Simply run npm run analyze
from the project folder. This will run a build of your site and automatically open the Webpack Bundle Analyzer visuals for your site's build files.
Huge ups to the following talented and rad folks who helped in countless ways. Thank you for all the support, code contributions, and discussions.
- π₯ @tuckercs
- π @iamkevingreen
- π§ @mikehwagz
- π @dictions
nickdimatteo.com Β Β·Β Github @ndimatteo Β Β·Β Instagram @ndimatteo