Brought to you and maintained by Trellis Commerce - A full-service eCommerce agency based in Boston, MA

Latest merged code from Dawn v15.2.0

Dawn + Tailwind CSS + Prettier Shopify Starter Theme

Shopify Dawn theme with Tailwind CSS & Prettier integrations

The starter theme includes an integration of:

Tailwind CSS

• Configured to use prefix: twcss- in order to not clash with Dawn’s existing styles

• There is the option to switch the order of the base.css & app.css stylesheets in theme.liquid if you want your Tailwind classes to take precedence over the base Dawn styles

Trellis' Prettier config with Husky pre-commit hooks

• Formats JS & CSS whenever a git commit is made
• Set up your own VSCode to apply Prettier formatting when a file is saved (optional)

Other Noted Modifications

• Set the default page width to 1440px and tweaked the desktop page width range to be 1200px to 1600px with a step adjustment of 10px (standard desktop width used at Trellis and allows for more fine tuning)
• There is a page template called noindexnofollow with the meta tag noindex, nofollow for any pages that need to be hidden from search engine site crawlers

Steps to Start Using this Starter Theme

1. Fork this repository & enable actions in the repo's Actions tab.

‼️	When forking this repo, make sure to change the settings in the forked repo under Settings > Actions > General > Workflow permissions to be Read and write permissions and check Allow GitHub Actions to create and approve pull requests for the Theme Check & Lighthouse actions to run

2. Clone the forked repo, navigate to the directory in your terminal, & run npm install.

3. In the theme section of your Shopify admin you can connect to a GitHub repository via “Add theme” button.

4. In your terminal, navigate to the cloned repo directory, and use the Shopify CLI to launch the development server to your store with shopify theme dev --store=mystore.myshopify.com and upload the theme with shopify theme share.

‼️	If you are working on a development store and are signed in via your partner dashboard, you must add a separate user in that Shopify store with admin rights and sign in with this new user when logging in using the Shopify CLI

You can add users in the store Settings:

Add GitHub secrets for Lighthouse CI Performance Evaluation Actions

‼️	This repo does not have the following secrets configured, which is why the Lighthouse action is failing.

First, make sure your Workflow permissions are set like below in order for the actions to run:

In your GitHub repo, navigate to Settings > Secrets > Actions and add the following repository secrets:

SHOP_ACCESS_TOKEN

• Settings > Apps and sales channels > Develop Apps > Create an app. Name it something like Lighthouse and give the app permissions of read_products,write_themes. Install the app and use the token value that will start with shpat_.

SHOP_STORE

• mystore.myshopify.com (ex. trellis-sandbox.myshopify.com)

SHOP_PASSWORD

• Need if Preferences > Password protection is enabled

SHOP_COLLECTION_HANDLE

• Collection with products manually added needs to be created and the handle used here
• Make sure data shows for the API request: https://mystore.myshopify.com/admin/api/2021-04/custom_collections.json?published_status=published&limit=1

SHOP_PRODUCT_HANDLE

• Select a product handle for a product that comes back from the API request: https://mystore.myshopify.com/admin/api/2021-04/products.json?published_status=published&limit=1

LHCI_GITHUB_APP_TOKEN

• To enable GitHub status checks via the official GitHub app, install and authorize the app with the owner of the target repo. If the repo is within an organization, organization approval might be necessary. Copy the app token provided on the authorization confirmation page and add it to your build environment as LHCI_GITHUB_APP_TOKEN

These secret values are used in the ci.yml GitHub workflow:

Install Shopify Liquid VSCode extension

• Includes Shopify Theme Check linting

Common local development commands

1. Before beginning any work, it is good practice to pull down the latest changes from the Shopify Dawn theme: git fetch upstream git pull upstream main

2. Add upstream link if you get the error fatal: 'upstream' does not appear to be a git repository run: git remote add upstream https://github.com/Shopify/dawn.git or git remote add upstream https://github.com/TrellisCommerce/shopify-tailwind-starter-base depending on which repository you want to pull updates from

3. Pull down changes from the theme editor: shopify theme pull -d

4. Anytime you add a Tailwind CSS class (remember to prefix it with twcss-), run the CLI tool to scan your template files for classes and build your CSS to assets/app.css: npx tailwindcss -i ./assets/app-tailwind.css -o ./assets/app.css --watch

• Run this command in a separate terminal, so it will continue to run while you are developing.
• Note that using a Tailwind CSS class without a space afterward when followed by a liquid tag causes compiling issues: lg:!twcss-px-[32px]{% endif %}'> But this does work: lg:!twcss-px-[32px] {% endif %}'>

5. Launch the local development server: shopify theme dev

---

Other Versions of the Starter Theme

Tailwind Admin Fields

• Branch

How Is It Different

Multiple admin fields have been added at the theme level, as well as at the section level, to allow for more granular control over the Dawn theme's settings and elements directly through the admin by inputting Tailwind CSS classes as values.

How To Use

First, decide if you want to configure the tailwind.config.js file to allow for your specific font families, sizes, colors, etc to cut down on the generated Tailwind CSS file from the start, or you can just jump in and take advantage of all the default Tailwind CSS classes.

1. Affect global animation timing & easing from Easing Functions Cheat Sheet in Theme Settings under Animations:

2. Affect global elements in the Theme Settings under the Tailwind CSS accordion:

3. Affect global elements and page-level sections under the Tailwind CSS heading for each Dawn element in the admin:

If Using in Conjunction with a Development Team

Optimizing CSS

In order to make all the Tailwind classes available for the editor in the admin, the following was added to the tailwind.config.js file to include ALL classes, as well as breakpoint & hover variants, and to add !important to each class to make sure it overrides any existing Dawn styles:

...
// safelist is added to provide all styles for design to add through the admin
safelist: [
   {
      pattern: /.*/,
      variants: ['xs', 'sm', 'md', 'lg', 'hover', 'group-hover'],
   },
],
// !important is added to override core Dawn styles for design
important: true,
...

If this theme is handed over to a development team who will be editing the code directly, the safelist array will need to be removed (ideal to also remove the important key, but that would require adjusting any conflicting Dawn styles) from the config file and the following added to the content array to have Tailwind recognize the classes added through the admin fields:

content: [
   ...
   './**/*.json',
],

If desired, run the Tailwind compile command to purge any unused styles (this step is optional as making a commit with changes to the tailwind config file will auto-generate a new app.css file after the commit is pushed, but this step will allow for a quick check on the proper purging of the classes): npx tailwindcss -i ./assets/app-tailwind.css -o ./assets/app.css

Lock Down the Admin Fields

To lock down the Tailwind CSS admin fields from being editied through the admin, run gulp in your terminal to transform all Tailwind text fields to checkbox fields instead and to add the following paragraph text to all Tailwind sections:

Tailwind fields are not editable through the admin at this stage. Please contact a Trellis engineer if changes are needed.

‼️	Note that toggling one of the checkboxes after running gulp will remove the contents of the tailwind admin fields. Since removing the fields also removes the entered values, swapping to a different field type preserves the values and does not allow for editing the values.

Code Review of Classes Inserted Through the Admin

It is recommended to have a separate branch & connected theme version created for the design team to use when adding in classes through the admin fields. This way, when it is time to merge in the changes from that branch to another theme branch, a pull request can be created and all the commits can be reviewed all at once instead of reviewing each individual commit generated by shopify[bot].