This theme uses
[email protected] BETA
*** Please star my repo to support my work ***
.envtaking example from
.env-exampleand add the following into
.env.productionand into 'site' directory and add your WordPress site url liks so.
Env variables from these file will be consumed by Apollo client on client side.
a. Headless CMS
c. wp-graphql - tested on ( v1.0.0 )
HCMS Header Menu
HCMS Footer Menu
You can also set text widgets in #HCMS Footer #1 and #HCMS Footer #2 under Appearance > Widgets in WordPress.
Create a Home Page ( if there isn't one already )and make sure you have a home page and Location rule is set to Home page.
If isn't already set your site title, description and logo from WordPress customizer.
WP Dashboard > Tools > Import > WooCommerce products(CSV): The WooCommerce default products csv file is available at wp-content/plugins/woocommerce/sample-data/sample_products.csv
yarn install # Run this for the first time. npm run dev # During development. npm run build # When ready for production.
** For development **
Your site is now running at
_Note: You'll also see a second link:
http://localhost:8000/___graphql. This is a tool you can use to experiment with querying your data.
npm run storybook
yarn workspace site add package-name
yarn workspace site remove package-name
yarn workspace gatsby-wooocommerce-theme add package-name
yarn workspace gatsby-wooocommerce-theme remove package-name
A quick look at the top-level files and directories you'll see in a Gatsby project.
. node_modules demos packages src .gitignore .site gatsby-browser.js gatsby-config.js gatsby-node.js gatsby-ssr.js package-lock.json package.json README.md
/node_modules: This directory contains all of the modules of code that your project depends on (npm packages) are automatically installed.
/src: This directory will contain all of the code related to what you will see on the front-end of your site (what you see in the browser) such as your site header or a page template.
src is a convention for source code.
.gitignore: This file tells git which files it should not track / not maintain a version history for.
.prettierrc: This is a configuration file for Prettier. Prettier is a tool to help keep the formatting of your code consistent.
gatsby-browser.js: This file is where Gatsby expects to find any usage of the Gatsby browser APIs (if any). These allow customization/extension of default Gatsby settings affecting the browser.
gatsby-config.js: This is the main configuration file for a Gatsby site. This is where you can specify information about your site (metadata) like the site title and description, which Gatsby plugins youd like to include, etc. (Check out the config docs for more detail).
gatsby-node.js: This file is where Gatsby expects to find any usage of the Gatsby Node APIs (if any). These allow customization/extension of default Gatsby settings affecting pieces of the site build process.
gatsby-ssr.js: This file is where Gatsby expects to find any usage of the Gatsby server-side rendering APIs (if any). These allow customization of default Gatsby settings affecting server-side rendering.
LICENSE: Gatsby is licensed under the MIT license.
package.json below, first). This is an automatically generated file based on the exact versions of your npm dependencies that were installed for your project. (You wont change this file directly).
package.json: A manifest file for Node.js projects, which includes things like metadata (the projects name, author, etc). This manifest is how npm knows which packages to install for your project.
README.md: A text file containing useful reference information about your project.
Signup on vercel.com
Click on Import Project and then add the configurations.
On vercel, make sure you add these evn vars from settings of the project:
npm i -g vercel
Now in the project root run
Add the following configurations
npm run build
npm run dev
https://www.npmjs.com/package/gatsby-woocommerce-theme Follow its readme on npm.js