gatsby-starter-shopify
shopify-packer
Our great sponsors
gatsby-starter-shopify | shopify-packer | |
---|---|---|
11 | 1 | |
306 | 182 | |
1.6% | - | |
0.0 | 0.0 | |
over 1 year ago | about 1 year ago | |
JavaScript | JavaScript | |
BSD Zero Clause License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
gatsby-starter-shopify
-
Gatsby starters: 30 free Gatsby templates for blazingly fast website building
GitHub source
-
What your process like building Shopify Theme with Gatsby?
Link to your store Follow these instructions here to link your Shopify store. Create a .env file with your Shopify store URL, password, and Storefront access token, using the .env.example file as an example. If you want to try with a development store, see the sample data and instructions here.
-
Gatsby & Shopify: Is it possible to setup user log-in on the frontend?
Would you say gatsby-shopify-starter is generally a good place to start wirh Gatsby & Shopify?
-
Is switching to Gatsby front-end for Shopify worth it? How is the dev support and integration? Can you still use Shopify apps?
Are you referring to the payment processing being done at a Shopify's domain instead of the original one? Like how on this gatsby-shopify-demo when clicking checkout it's redirected to https://gatsby-dev-30k-sku.myshopify.com/56348803256/checkouts/....?
-
Gatsby SSR
Update: I actually realised that I didn't have nginx-proxy container running! However I'm still having issues accessing pages that are served via SSR.. i.e. '/search', when running 'gatsby serve' behind the nginx reverse proxy. I just get a 404. I can access '/search' when running locally (on port 9000) but not when it's dockerized. I'm aware it may be the case that SSR in Gatsby refers to service rendering purely to produce a build but when I build and deploy the static assets to be served under nginx '/search' still produces a 404. In a nutshell '/search' doesn't work unless being accessed by 'gatsby serve' with no reverse proxy. I've been voicing my troubles on this GitHub ticket: https://github.com/gatsbyjs/gatsby-starter-shopify/issues/57
- What are the advantages of using Shopify StoreFront API to instead of pulling product catalog from a headless CMS?
-
E-Commerce Stack Suggestions
I absolutely love Gatsby, but more so for marketing sites. When it comes to Ecommerce, Gatsby developed a Shopify starter: https://github.com/gatsbyjs/gatsby-starter-shopify
-
Gatsby + Shopify: Can you do collection page filtering? Or would Next.js be a better choice?
If you feel like using Gatsby instead, the other store I linked can be forked from here.
-
[HIRING] Gatsby Developer for Headless Store - Shopify and CMS
My budget for now is around 1000-1100$. Because this project is without design and styling, and because there is a huge Gatsby Shopify Starter I think a lot of work has already been done.
shopify-packer
-
Fast Shopify development with hybrid Debut theme
Shopify Packer written by Eric Hayes is probably the best thing happened to Shopify theme development since Shopify stopped supporting Slate. It's everything we all hoped for and that's a promise. Packer uses Webpack 5 with zero config to compile, bundle, split and minify your modern development technologies and start a server for development with hot module reloading actually working perfectly. It can also create, list and manipulate (delete, download, deploy etc) themes from your shop which is a lifesaver sometimes. I also love using Eric's Shopify Packer because it uses SCSS, Stylelint, ESLint, Babel and PostCSS. It can analyze bundles and have multiple entry points for templates and layouts. It's actually a CLI tool that’s installed globally and you can start a new project or integrate Packer with an existing theme in ridiculously little time. Most importantly you can easily customize all settings for the site and webpack if needed. Eric also provides quick support for the packer so i would highly recommend it and also buy him a beer because he deserves one for this!
What are some alternatives?
next-shopify-starter - Nextjs + Tailwind CSS + Shopify Starter
Symfony Encore - A simple but powerful API for processing & compiling assets built around Webpack
js-buy-sdk - The JS Buy SDK is a lightweight library that allows you to build ecommerce into any website. It is based on Shopify's API and provides the ability to retrieve products and collections from your shop, add products to a cart, and checkout.
shopify-theme-lab - Shopify theme development environment using Liquid, Vue and Tailwind CSS. Built on top of Shopify CLI 🧪
gatsby-plugin-apollo-client - 📡Inject a Shopify Apollo Client into the browser.
themekit - Shopify theme development command line tool.
storefront-api-examples - Example custom storefront applications built on Shopify's Storefront API
shopify-bare - Shopify starter theme that provides Javascript modules(ES6 and node_modules), tree-shaking, Live Reloading/ Hot module reloading, Tailwind Css w\ nesting & imports purges unused CSS, minify your built files, compress your images, and use quick commands to develop easier.
Shopify-api-node - Node Shopify connector sponsored by MONEI
b-creative
commerce - Next.js Commerce