Resources

Tools and notes from the work.

Notes on the decisions behind the work, tools I built from client work and a free guide to the whole plan.

Notes

Public note
Why translations need their own release step.
What moves with your theme code, what stays tied to Shopify resources and how I plan the translation handoff.
Read the note

Tools

Shopify app / Access by enquiry
Stage & Translate.
An app I built from client work to carry supported translations from staging to the live theme after the code merge.
Explore the app

Not ready to commit? Take the whole plan.

Five choices decide whether a Shopify store grows or gets rebuilt: headless or Liquid, which apps, what lives in the backend, how to run several stores. How I make them, and why. Free.

Get the decision plan

Why this matters
Made early, these choices mean Plus, a second store or a new developer is a next step, not a rebuild.
Headless or Liquid
Start on Liquid. Go headless when the store needs the server side, and only with an experienced developer.
Which apps to use, and which not
Apps that configure the backend. An app with a frontend only when it brings its own backend, never to make up for the theme.
What belongs in the backend, and what in the theme
If you would keep it after swapping the theme, it is a metafield or metaobject.
Ways to run several stores
A second store only for entity, permissions, teams or design. Then a modular theme, a central app on Plus, or headless by domain.

Notes

Why translations need their own release step.

Tools

Stage & Translate.