Case study — Retail e-commerce
Al-Khalifa Store.
Two inks and a yellow charge: a store built for the phone in your hand.
Try it live
The real thing, right here.
The brief.
Most of the store’s customers shop on their phones. The client knew what they didn’t want: no cream, no beige, no dark mode, no red buttons. What was left had to still feel bold.
The dig.
We wrote a design constitution. Two inks, near-black and pure white, and one accent: a yellow that carries every button, chip and hover. Yellow is hard to read, so it ships as three tokens, one for fills, one for text on a fill, one for text on paper. Mobile first, with a dock at the thumb.
The shine.
A store and an admin that follow the same rules on every screen, backed by a Go API and Postgres, all started with one docker compose up.
The system
How it looks, and why.
Black, white, and a charge of yellow. Flat, loud, fast.
#F6C32CThe fill: buttons, chips, badges#1A1A1AText and the dark band#FFFFFFPlain white. Not cream.#00AA3CStatus only#9B111EStatus only- Never white text on yellow (1.8:1). Use the volt-ink token (~10:1).
- Never hard-code a hex in a component. Every color is a variable.
- Every shadow token is set to zero. The store is flat.
- Next.js
- Tailwind v4
- Go · gin
- PostgreSQL
- goose
- Docker
Worth stealing
Ideas from this one.
One yellow, three jobs
volt for fills, volt-ink for text on a fill, volt-text for yellow-ish text on white. The most common color mistake is gone by design.
A written constitution
The rules live in the repo, so every screen (and every helper) follows them.
Shadows turned off at the root
Instead of avoiding shadows, the tokens are zeroed. Nothing can add one by accident.
Built for the thumb
A bottom dock and a tab bar with fixed heights, so the store feels like an app.
Seen enough? Go and use it.
alkhalifa.shop