...
Step-By-Step Theming Process
Pull a copy of the theme designer branch with
git clone git@bitbucket.org:aspenwareunity/commerce-theme-builder.git
Run Theme Designer with the
yarn dev
command in terminalCreate a duplicate of the Clean Theme directory and rename it to the current client.
Update the _colors.scss file in the client theme directory with all of the client color options.
Update the _variables.scss file in the client theme directory with the paths to the correct image files.
Update the _typography.scss file in the client theme directory with the clients font information
...
.
...
...
Run Theme Designer with the yarn dev
command in terminal
In the Theme Designer source files, open
layouts/default.vue
andcheckout.vue
. Locate the scss import statement that targets the client theme. Change the path in both files to point at the client theme directory you are working on. This will make Theme Designer load that clients SCSS into the Design window.Remove any CSS or Mixins if they exist in the _theme.scss file.
In Theme Designer, in Presentation Mode, set all of the theme option controls to match the client choices.
Enable Developer mode, and click the "Export All Mixins" button.
Copy the mixins from the dialog box and paste them into the clients _theme.scss file. Make sure they are uncommented and save the file.
In Theme Designer, enable Preview Mode. You should now see the mixins from the clients _theme.scss file being applied.
While still in Preview Mode, make any additional configurations necessary to the mixins in the clients _theme.scss file and ensure they appear correct in the Theme Designer preview.
Copy the clients entire theme directory from Theme Designer over to the Theme directory in commerce.
Fire up a local instance of Commerce, set the environment to the client and QA the entire theme.
If it looks good, commit the theme to Commerce source.
IMPORTANT: DO NOT Commit any changes you made in the Theme Designer source.
Known Limitations and Bugs
There is a limitation with the checkout page in demo mode in that it will not retain the settings configured on other pages. This should be resolved in the future.
A code change is necessary to display anything other than the “Clean Theme”, so when developing a theme there is no UI method to view other themes.