file 01/06 · brief
home / projects / lexisia
// case study · launch site

An audience gathered
before day one.

A pre-launch site for Lexisia: six scroll stops, four capture forms, and an admin panel that shows who signed up and where the rest stopped.

client · lexisiarole · design + full-stacksince · jul 2026
live in production ↗
Lexisia launch site · live screenshot
the story
// 01 · the challenge

The people come
before the paperwork.

Lexisia is a legal-advocacy foundation opening in The Hague, and it needed organisations, volunteers, donors and a launch list, gathered while the case desks were still on paper.

Six stops came out of that, with a form waiting at the last four. Every answer lands in D1, inside Lexisia's own Cloudflare account.

// 02 · what we built

Six stops,
four doors.

A scroll that asks as it goes
The route runs stop by stop, so the story earns the ask before the first form appears.
One form per audience
Organisations, volunteers, donors and the launch list each get their own questions. A single shared inbox was never going to sort them.
Junk stopped at the edge
Turnstile and a honeypot on every form, checked in the worker before a row is written. Four public forms, no moderation queue.
Drop-off you can see
Each form reports viewed, advanced and submitted to Analytics Engine, and the gated dashboard reads it back.
// 03 · the stack

Boring where it should be.

Proven parts, assembled carefully. Novelty goes into the product, not the plumbing.

frontend
React + Vite
edge
Cloudflare Workers
data
D1 + Analytics Engine
access
Zero Trust
ui/ux designfrontend + backend buildcloud infrastructure
// 04 · in production

Open, and taking names.

6 stopsone scroll from who we are to stand with us · the first two tell the story, the last four ask.
1 workersite, api and admin all served from one worker at the edge · no server to patch.
day onethe forms were collecting before the organisation opened its doors.

A word from the Lexisia team is on its way.

dr. hashim rifai · founder, lexisia