cms VS gatsby-starter-shopify

All you need is to choose CMS with an API-first approach and start building websites and applications in a composable way. BCMS headless CMS is a tool that can help you achieve so, whatever method you choose: hub-and-spoke approach or building composable architecture from scratch.

A fully functional job board with Gatsby.js, Tailwind, and BCMS. Whether you are looking to build a job board for your company or a stand-alone job board website - this starter is a great choice.

To start with, you'll need to create an account on the BCMS website. Once your account is created, you can either decide to use the cloud version of BCMS or the self-hosted version. Whichever you choose make sure to create an account because you will need it to login later.

For this article, we will be using the locally hosted option. Check out this tutorial on how to set up BCMS locally, or head to the BCMS website to sign up for the cloud version. Now that you've set up the environment let's move to the next step.

You should also have a BCMS account; to create one, go to https://thebcms.com.

We had the same problem when it came to customization with certain CMSs. But we started using BCMS.

You can check out BCMS. Here's the documentation: https://docs.thebcms.com/

Hey, I'll be happy to recommend you to try out BCMS ( https://thebcms.com/ ), a modern headless CMS which is very easy to work with Vue and Nuxt.js. I'd recommend working with Nuxt just because it has better SEO optimization out of the box, so not much hustle is required on that end. As for how to use BCMS with Nuxt.js you can read more in this blog post: https://thebcms.com/blog/how-to-connect-bcms-and-nuxtjs. You can even set up your FREE instance of BCMS locally and test everything before you decide to use it!

Headless CMS definitely! https://github.com/bcms/cms

GitHub source

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.

Would you say gatsby-shopify-starter is generally a good place to start wirh Gatsby & Shopify?

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/....?

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

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

If you feel like using Gatsby instead, the other store I linked can be forked from here.

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.