All projects
ShopifyStorefront2026

DFYNE HOMEPAGE

DFYNE runs drops. A collection lands, the homepage has to lead with it that morning, and the date is set by the shoot, the campaign email and the paid spend — not by whoever is free to build the page. I built the sections the homepage is made of, so the people running a drop can put one together themselves.

Client
DFYNE
Scope
Configurable homepage sections — heroes and product rails
Timeline
2026
Stack
Shopify Plus, Liquid, theme sections, Klaviyo
Status
Live on both storefronts
Live

What the page has to carry

The homepage is never showing one thing. The version in these screenshots is running three campaigns at once: Dynamic, the Anisia collaboration, and the 5th Birthday collection. Each gets a full-bleed hero with its own artwork and its own two calls to action, and a product rail underneath it with its own heading, its own colourways and its own link through to the collection.

That is seven blocks of page. Built one at a time they are seven things to maintain, and every future drop is an eighth. Built once they are two things used repeatedly — which is what they are.

What I did

Two sections do the work.

A hero takes a piece of artwork, the headline set over it, and up to two buttons pointing wherever that campaign needs them to. A product section takes an eyebrow line, a title, a row of colourway thumbnails, a link through to the full collection, and the rail of products underneath. This page uses the hero three times and the product section four, and there is nothing about Anisia, or Dynamic, or a birthday, written into either of them.

The rail reads from a collection rather than a hand-picked list, which puts the decision where it already lives: merchandising a drop is a merchandising job, and the homepage follows it. The badges on the cards — New, Limited Edition, Oversized, Sold Out — come from the product rather than being typed into the section, so a size selling out mid-drop updates the page without anyone touching it.

The same sections carry to mobile, where the rails scroll sideways and the navigation collapses into a drawer that swaps its whole tree, promo tiles included, between womenswear and menswear.

The newsletter at the foot of the page is Klaviyo, and that integration is mine too — the DNS records that let it send as DFYNE, and the mailer itself.

What a drop needs from me now

The test these were built against: can a campaign go live without a developer in the room.

The artwork and the words
The hero image, the headline over it, both buttons and where each one points are content on the section. A new campaign is a new set of values rather than a new block of markup, and nobody waits on a deploy to fix a button that says the wrong thing.
Which products, and in which colourway
The rail is fed by a collection and the thumbnails above it filter by colour. Both are things the team changes anyway while setting a drop up, so the homepage updates as a side effect of work that was already happening.
Where it sits on the page
Sections can be reordered, duplicated and switched off. Which campaign leads the page on the morning of a launch is a decision made on the morning of the launch, by the people whose decision it is.

The evidence

The same product section, a different collaboration. Four thumbnails instead of six, because that is how many colourways the drop has.
And again, further down the same page. The Sold Out badge on the third card is the product saying so, not somebody remembering to.
The same sections on a phone. The rails scroll sideways, each card gains a quick-add button, and the footer columns become accordions.
The same sections on a phone, beside the drawer that replaces the navigation. Womens and Mens swap the whole tree, promo tiles included.
The signup block is Klaviyo. I set up the DNS so it sends as DFYNE, and built the mailer behind it.