Marcus Klein
July 1, 2026 · 10 min read
What Liquid actually is
Liquid is Shopify's templating language: server-rendered, sandboxed, and deliberately limited. Its limits are its virtue — a Liquid store cannot crash your server because your server is Shopify's server.
Understanding what Liquid cannot do (background jobs, arbitrary network calls) shapes every architecture decision built on it.
Section-first architecture
OS 2.0 means every page is composed of sections — self-contained units with their own schema, styles, and settings. The senior pattern: small sections, strict schemas, and a marketing team that can restyle without you.
A section schema is a contract with your marketing team. Write it like one: clear settings, sensible defaults, and blocks that map to real editorial needs.
The performance pitfalls
Unnecessary requests per section, unoptimized image tags, render-blocking scripts from apps, and Liquid loops that paginate thousands of products. Each is a classic — and each is avoidable with discipline.
The fastest Liquid stores share one habit: they audit what every section requests, and refuse anything that cannot justify it.
Metafields and Metaobjects: modeling beyond products
Store data that is not product data — brand stories, lookbook entries, store locators — in Metaobjects, and expose them through section schemas. This replaces the old 'page of pages' hackery.
Model first, template second. A clean data model makes the Liquid trivial; a messy one makes everything hard.
When Liquid is not enough
Checkout logic moves to Functions. Deeply dynamic storefronts move to Hydrogen. Custom admin workflows move to app development. Liquid remains the heart, but senior work means knowing its borders.
The developers who ship fastest are the ones who reach for the right tool instead of the one they know.
Frequently asked questions
Topics
