Getting Started
Last updated
Last updated
v18+
A package manager -> , , or will work.
v3
The tech stack specified .
Clone the Accelerate repository from Github and install it locally by running pnpm install
(or yarn / npm).
Create a new branch with a prefix of your name, i.e. felix/dev/{name_of_feature}
Check that the .env
is configured properly
The SHOPIFY_THEME_FOLDER
variable sets your current working directory for all development scripts. It can be set in the package.json
inline your dev script, or you can change it in the .env file based on what store you are working on.
Ensure that your .gitignore
and IDE is set to not add any files from the /themes
directory to the main Git repository.
Always make a copy of the theme that you want to work on, as it's difficult to know who made changes beforehand.
Configure your npm scripts in the package.json
with the following 2 scripts:
Example
Once the configured, and if it is the first time working on the theme,
Run the pull
script to download the theme onto your local machine.
Use your terminal to cd themes\\{store_name}
Run git init && git add . && git commit -m "Initial Commit"
to initiate a Git repository for only the theme files.
You also want to setup a GitHub repo using the platter-base-{store-name}
naming convention and set it as a remote.
If you previously worked on the store, make sure that any previous changes on your local machine are committed first, then run the pull
script to get any changes from the theme. It's important now to check if there are any potential breaking changes. Any changes in the templates/*.json
files are what the merchants have done within the Theme Editor and will not be affected by any dev tools.
Before starting development, it's important to make sure that any changes that were pulled
in are committed, so that you have a clean slate to start from.
Make sure that your dev
script is configured for the correct theme.
For Windows
Alternatively, you can set it directly via the ./.env
file.
Adding a space before the ampersands, as follows, will not work on Windows. SHOPIFY_THEME_FOLDER=themes/{store_name} &&
For Mac
Now you can run pnpm run dev
in your terminal and in a second terminal pnpm run shopify:serve
to push your changes up to the Shopify Store. This will also open a new window in your browser to see your changes as you make them.
Performance Best Practices
Clone the Accelerate repository from Github and install it locally by running pnpm install
(or yarn / npm).
Create a new branch with a prefix of your name, i.e. felix/dev/{name_of_feature}
Check that the .env
is configured properly
The SHOPIFY_THEME_FOLDER
variable sets your current working directory for all development scripts. It can be set in the package.json
inline your dev script, or you can change it in the .env file based on what store you are working on.
Ensure that your .gitignore
and IDE is set to not add any files from the /themes
directory to the main Git repository.
Configure your npm scripts in the package.json
with the following 2 scripts:
Example
Once the configured, and if it is the first time working on the theme,
Run the pull
script to download the theme onto your local machine.
Once completed, use your terminal to cd themes\\{store_name}
Run git init && git add . && git commit -m "Initial Commit"
to initiate a Git repository for only the theme files.
You also want to setup a GitHub repo using the platter-base-{store-name}
naming convention and set it as a remote.
If you previously worked on the store, make sure that any previous changes on your local machine are commited first, then run the pull
script to get any changes from the theme. Its important now to check if there are any potential breaking changes, Any changes in the templates/*.json
files are what the merchants have done with the Theme editor and will not be affected by any dev tools.
Before starting development, it's important to make sure that any changes that were pulled
in are committed, so that you have a clean slate to start from. Now you need to make sure that your dev
script is configured for the correct theme.
For Windows
Alternatively, you can set it directly via the ./.env
file.
Adding a space before the ampersands, as follows, will not work on Windows. SHOPIFY_THEME_FOLDER=themes/{store_name} &&
For Mac
Now you can run pnpm run dev
in your terminal and in a second terminal pnpm run shopify:serve
to push your changes up to the Shopify Store. This will also open a new window in your browser to see your changes as you make them.
(including all subsections)
The best example of semantic HTML we've seen is on . Review their source code by inspecting the page on Chrome Dev Tools. You will see a strict adherence to <section> <header> <main> <footer> tags.
Same as with the integrated dev tools, unless you are working on your own development store () always make a copy of the Theme that you want to work on, as you never know who made changes beforehand.