Helix
Design systemA design system concept built to answer one question: how much of a product interface can be decided once and reused everywhere?
- Design systems
- Tokens
- Accessibility
- Documentation
The product page as the whole argument.
A storefront concept for a considered-purchase catalogue, where the product page has to do the work a showroom used to.
Overview
Status
Internal design and engineering exploration
Disciplines
Capabilities used
For high-consideration goods, the checkout is rarely the problem. The product page is. It has to answer material questions, handle comparison, and survive being the only page someone sees.
We explored what a storefront looks like when the product page is treated as the primary design surface rather than a template slot.
Approach
We wrote the buyer objection sequence first and mapped each objection to a specific element on the page, then removed anything that answered nothing.
A large-format editorial layout with typographic specification tables, comparison built into the page rather than hidden behind a modal, and a persistent purchase bar that never obscures content on small screens.
Headless storefront on Next.js with statically generated product pages, cart state on the edge, and an image pipeline that keeps large photography inside a strict performance budget.
Outcome
A complete storefront template set — listing, product, comparison, cart, checkout — with a documented performance budget and an accessible variant-selection pattern.
Why there are no numbers here. This is an internal concept, not a client engagement. We do not publish conversion rates, revenue or satisfaction figures that no real deployment produced.
Start here
If this is close to the problem you have, tell us about it. We will be specific about how we would approach yours.