work
PROJECT
YEAR
TIMELINE
TEAM
STACK
ROLE
indffrnt. — the studio, as a build.
Our own surface, built the way we build for clients. A Shopify Liquid theme with an agent rail instead of a nav, edge-rendered, shipped as proof.
Problem
A studio site usually argues for the work in a deck. We wanted the site to be the work: a live, fast, agent-routed surface a skeptical commerce lead could read in two minutes and trust.
The site is the product. Same as the work.
Approach
No marketing nav. An agent rail routes intent — see the work, scope a build, read the notes. Every scene is a real Shopify page with its own URL and native view transitions. Case studies are metaobjects, so the archive is data, not hand-built pages. Lit islands hydrate for parity; the whole thing runs on Liquid at the edge.
- wk 01 — intent map · agent rail over nav
- wk 02 — Liquid component tooling · Lit islands
- wk 03 — case_study metaobjects · archive as data
- wk 04 — live · view transitions · edge cache
04
WEEKS INTAKE TO LIVE
0.7s
LCP P75, EDGE
100
CWV
5
SENIOR · NO JUNIOR
Outcome
- The surface routes intent instead of selling — visitors land on the work, not a pitch.
- Adding a case study is one metaobject entry, not a new page build.
- The studio runs the same stack it sells: Liquid, Lit, edge.