Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time


A proof of concept for an e-commerce store powered by Contentful, Gatsby.js, Stripe, Clay, and hosted by Netlify.

This project has been updated to use Gatsby v2

This project uses the old version of Stripe Checkout. For an updated e-commerce Gatsby + Stripe integration, see my project dragon-mart.

The Goal

I wanted to create a simple e-commerce solution that leverages the awesomeness that is static generators, while still giving clients a CMS to manage their inventory. My goal is always to get off of using WordPress whenever a CMS is required by a client. Bye bye WordPress!

To Run

Of course you'll need to create accounts and download all the things you'll need to download to use the above services and tools. Once that's all set up, and you've cloned the repo:

  1. Run npm install.
  2. In Contentful, create a Product content type. To run this example exactly as is, your content type should have six fields:
    • Name (short text)
    • Product Id (integer)
    • Price (integer)
    • Images (media, many files)
    • Colors (short text, list)
    • Sizes (short text, list)
  3. Make a product in Contentful. Mine, of course, was a unicorn! The images are included as a zip file in this project.
  4. Make your own .env file at the root of the project, and put your Contentful Space Id and Access Token there.
  5. For Clay serverless function, I basically just used the code here. If you want to change the implementation, feel free to fork what Kareem has and edit it! My version actually just returns a "success" object and doesn't do any charging. In the front-end code, you'll just need to change the endpoint URL in cart.js to point to your own endpoint.

What I Learned / Remaining Questions

First, though I love Contentful, it might have made more sense to handle inventory in Stripe itself. This way I could have treated it more easily as inventory, with specific stock, SKUs, etc. That beind said, I know there are ways to alter the data that gets stored in Contentful through their Management API, so I also could have leveraged that. An extension of this project would be to implement that functionality.

Second, creating a Gatsby plugin to inject Stripe's Checkout JS library was surprisingly simple, thanks to the examples provided by Gatsby. I have since made two standalone Gatsby / Stripe plugins for implementing Stripe Checkout (download on npm) and Stripe Elements (download on npm).

Third, going serverless with Clay was great! Such an awesome team, and such a great product. I especially like how easy it is, the logs, and the ability to easily copy and customize what others have done.

Fourth, this project could be extended / improved in (I'm sure) a multitude of ways. Notably:

  • Implement Redux (mostly for funsies)
  • Use Contentful's Management API to show how to decrease inventory and ultimately show if a product is 'sold out' on the front-end
  • Make a store with multiple products
  • Implement Stripe Elements instead of Stripe Checkout
  • Have the Clay serverless function e-mail a receipt to the customer and an order summary to me

If you're interested in tackling any of these things, feel free to fork! Also, I'm sure my current code could use some refactoring or cleaning up. Feel free to fork and go wild! :) Any questions or comments, get in touch via Twitter!


A proof of concept e-commerce store leveraging Contentful, GatsbyJS, Stripe, and serverless via








No releases published


No packages published