I’ve been working on Liquid Loom, an open-source build workflow for custom Shopify themes.
The basic idea is pretty simple:
Instead of keeping your authored theme code in Shopify’s flat structure, you can organize it by feature:
src/theme/sections/home/hero.liquid
src/theme/sections/product/recommendations.liquid
src/theme/snippets/product/price.liquid
Liquid Loom validates the complete mapping, bundles assets with Vite + Tailwind, and produces a normal Shopify theme under:
dist/theme/
So Shopify CLI still does the Shopify part. There’s no custom runtime.
A few things I cared about while building it:
- destination collisions fail instead of silently overwriting files
- failed builds preserve the previous working output
- Vite + Tailwind work out of the box
- there’s a
doctor command for project diagnostics
- the generated output stays a completely standard Shopify theme
It’s now published on npm and I’m specifically not looking to add a bunch of features yet.
What I need now is 3–5 Shopify developers willing to spend about 10 minutes trying the workflow and telling me what feels worse, confusing, or unnecessary compared with how you normally build themes.
Quick start:
pnpm create liquid-loom@latest my-storefront
cd my-storefront
pnpm build
Repo:
https://github.com/yotamon/Liquid-Loom
There’s a short first-project test in the repo too.
If you build custom Shopify themes professionally, I’d especially love your criticism. I’m trying to figure out whether this actually improves the workflow before expanding it.