During the Shopify theme development process it may be appropriate to have features change slightly depending on whether they’re being used by a customer, a developer or a test suite. For example, if we have an integration in our store, we might want to send API requests to a testing endpoint whilst developing, or running tests on a staging theme, before connecting to a live endpoint when we publish the changes. We can’t trust that we’ll always remember to change this endpoint back to live before deploying to a live theme, so we can avoid the risk by using an environment dependent setting to control this.

It's often tempting to keep our HTML components clean by keeping class names simple. In my experience nesting CSS selectors to accomodate simpler class names can be quite problematic though. I've written this post to outline some of the issues I've found that seem to be ignored elsewhere.

I’ve been keeping a close eye on the development of Slate over the past few months, and a recently approved pull request caught my attention. The new Slate Sections Plugin improves section management by separating schema and translations from the liquid templates.

Ever wanted to integrate a Twitter feed into your static website? In this tutorial we'll integrate one into a Nuxt site deployed on Netlify and we'll learn how to make Twitter trigger redeployments for our website.

A lot of discussion is made regarding how we structure our CSS in order to maintain readability and ease of use. In some cases this causes our HTML elements to start piling on extra classes. I'm proposing that we pay more attention to keeping our HTML readable.