From 8fb6c7b206472d0fa0a79f4097f783934c409ee3 Mon Sep 17 00:00:00 2001
From: B <curciobelen@gmail.com>
Date: Wed, 26 May 2021 19:14:34 -0300
Subject: [PATCH] Update README.md

---
 README.md | 21 +++++++++++++++++++--
 1 file changed, 19 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 941b1699b..4e7a1aa1e 100644
--- a/README.md
+++ b/README.md
@@ -7,8 +7,9 @@ Start right now at [nextjs.org/commerce](https://nextjs.org/commerce)
 
 Demo live at: [demo.vercel.store](https://demo.vercel.store/)
 
-- Shopify Demo: https://shopify.demo.vercel.store/
-- BigCommerce Demo: https://bigcommerce.demo.vercel.store/
+- Shopify Demo: https://shopify.vercel.store/
+- Swell Demo: https://swell.vercel.store/
+- BigCommerce Demo: https://bigcommerce.vercel.store/
 
 ## Features
 
@@ -40,6 +41,22 @@ Next.js Commerce integrates out-of-the-box with BigCommerce and Shopify. We plan
 
 Open `.env.local` and change the value of `COMMERCE_PROVIDER` to the provider you would like to use, then set the environment variables for that provider (use `.env.template` as the base).
 
+The setup for Shopify would look like this for example:
+
+```
+COMMERCE_PROVIDER=shopify
+NEXT_PUBLIC_SHOPIFY_STOREFRONT_ACCESS_TOKEN=xxxxxxxxxxxxxxxxxxxxxxxxxxxx
+NEXT_PUBLIC_SHOPIFY_STORE_DOMAIN=xxxxxxx.myshopify.com
+```
+
+And change the `tsconfig.json` to resolve to the chosen provider:
+```
+  "@framework": ["framework/shopify"],
+  "@framework/*": ["framework/shopify/*"]
+```
+
+That's it!
+
 ### Features
 
 Every provider defines the features that it supports under `framework/{provider}/commerce.config.json`