Lumen & Lot
A website for a design studio that doesn't exist, where the sunlight is calculated, not drawn.
- Role
- Design and build
- Year
- 2026
- Timeline
- 10–17 November 2026
- Team
- Solo, with Claude Code
- Stack
- Next.js, React, TypeScript, Tailwind CSS, Zod, MDX, SunCalc, React-pdf, Vercel
01 — The 30-second version
The 30-second version
- Problem
- Building a website isn't just about how it looks. It's about how it feels when someone uses it.
- What I did
- I made up a design studio, Lumen & Lot, and designed and built its whole website, where the sunlight is calculated, not drawn.
- Result
- Underneath, it's one design system, and it scores 98 to 100 on PageSpeed.
02 — Overview
The homes are sample content; the website is real.
I made up a design studio, Lumen & Lot, and designed and built its whole website. It’s a design-build studio that designs, builds and furnishes small homes in Toronto, the Hudson Valley, Copenhagen, Lisbon and London, and the site reads like a printed monograph, not a store.
The homes are sample content. The website is real.
03 — The core tension
Building a website isn't just about how it looks, it's about how it feels when someone uses it.
Building a website isn’t just about how it looks. It’s about how it feels when someone uses it.
A studio site like this lives or dies on the things people actually do with it: see how the light falls, picture the finishes, look closer at a piece in a room, compare homes, send a brief. Each of those had to work properly, for everyone, not just look good in a screenshot.
Each of those had to work properly, for everyone, not just look good in a screenshot.
04 — Decisions made, and why
If you can't reach it with Tab, it isn't finished.
The sun on this floor plan isn’t an animation I drew.
It’s worked out from the home’s real location and the date you pick. A few rules make it look right:
- A window only lets sun in when the sun is up and less than 90° off the way the window faces.
- Walls are 30 cm deep, so low sun gets cut off at one side of the window.
- The patch on the floor runs from the sill to the top of the window, stretched by the sun’s angle.
The same numbers fill a table of sun hours for each room, so a screen reader gets them too. Winter and summer really look different. That was the point.
One room, three palettes.
The hard part of a palette switcher isn’t the button. It’s making the photos comparable. If the camera moves or the sofa changes, you’re not comparing finishes anymore. So I generated each set in Figma AI from one shared description of the room and the camera. Only the finishes change. The photos and the finishes list switch together. Your choice also goes in the link, so you can send someone the exact palette you like.
Hotspots that work with a keyboard.
Shoppable photos usually stop working the moment you use a keyboard. Here each hotspot is a real button, named after the piece. The card sits right after its marker, so Tab goes marker, card, next marker. Escape closes it and takes you back to the marker. The focus ring needed its own rule. The site’s clay ring can get lost on a photo, so anything that sits on a photo gets an ink ring with a light halo. It shows on light and dark images.
If you can’t reach it with Tab, it isn’t finished.
The before/after slider is one HTML input.
A normal range input sits on top of both photos, fully transparent. The before photo is cut to wherever the slider is. So arrow keys, Home and End, mouse and touch, and screen readers, which read “40 percent before, 60 percent after”, all came free.
Compare and brief.
You can compare three homes side by side, in square meters or feet, and in dollars, euros or pounds. When you’re ready, a six-step brief turns into a PDF right in your browser. Nothing is sent anywhere.
05 — The design system beneath
The docs can't go out of date, because the build won't let them.
Every colour on this site is a token, and the build checks it.
- All the tokens live in one file. Tailwind’s default colours are turned off, so only mine exist.
- ESLint blocks raw hex and px values in components.
- The /system page reads that file when the site builds. If a colour or type size has no description, the build fails.
That last rule does the most. The docs can’t go out of date, because the build won’t let them.
Colour
- Paper#F4F1EA
- Ink#161513
- Muted#6B675E
- Clay#B4532A
- Moss#4B5A3C
- Rule#D9D4C8
Type
- Instrument SerifDisplay
- Inter TightBody
- Geist MonoLabels
06 — The build
The list is where the decisions lived, so nothing got decided twice.
I built this site with Claude Code, one phase at a time. Ten phases: setup, design system, content, home, residences and daylight, palettes, compare and brief, projects, journal, launch.
The project file has a Decisions list. At the end of every phase, anything we settled went into it: how dates work, which colours can be used for text, why the hotspots are buttons. The next phase started from those decisions instead of guessing again.
Claude Code wrote a lot of the code. The list is where the decisions lived, so nothing got decided twice.
07 — What was designed
Seven residence pages, a compare tool, a six-step brief and a living design system.
Home · Residences · Seven residence pages, each with the Daylight Explorer, palettes, finishes and specifications · Shop the Room · Compare · A six-step brief · Projects, with a before and after slider · Journal · Studio · Colophon · A living design system page.
The site
Signature features
On a phone
08 — What it moved
98 to 100 on PageSpeed, on mobile, with full-screen photos.
- on PageSpeed, on mobile, with full-screen photos
- 98–100
- for the page to show on a phone
- 0.9 s
- layout shift while it loads
- 0
- for each photo on a phone
- 14–26 KB
98 to 100 on PageSpeed, on mobile, with full-screen photos. What did most of the work:
- Each photo reaches a phone as 14 to 26 KB.
- The first photo starts loading right away, so the page shows in 0.9 seconds.
- Nothing jumps while it loads. Layout shift is 0.
- No cookies and no analytics, so there’s nothing extra to load.
The one slower number is Speed Index on the home page. The moving city list and the rising headline keep the screen changing, on purpose. I kept them.
09 — Looking back
Before writing a custom drag handler, check what the browser already does.
Before writing a custom drag handler, check what the browser already does. And if you can’t reach it with Tab, it isn’t finished. Building a website isn’t just about how it looks. It’s about how it feels when someone uses it.
10 — Credits
Credits
- Design and build
- Emmanuel Onugwu
Next project


