Case study · 06 / 12
Gilmore
A studio website you paint with the cursor
- Year
- 2026
- Focus
- Next.js
- Status
- Live
A website for an independent design and engineering studio, built in Next.js 16 and TypeScript, where the two signature pieces, the hero and the globe, are written by hand on a canvas.
A studio that sells craft cannot arrive on a template. Gilmore had to prove its point in the first three seconds, so the hero is an interaction and not a picture: move the cursor and a second image bleeds through the first like wet ink, then heals. Further down, a dotted globe shows where the studio works and what time it is there, and you can spin it by hand. I wrote both from scratch on a 2D canvas, with no WebGL and no map library, because the heavy route would have cost more in load time than the effect was worth. Around them sits a quiet system: one scale that adapts to every screen, a loader that waits for the real picture, and motion that steps aside when a visitor asks for less.
What it does
- 01Reveals a second image under the cursor, in a trail that fades like ink
- 02Spins a dotted globe by hand, with studio cities, local times and arcs between them
- 03Opens with a counting loader that lifts only when the hero picture is ready
- 04Scrolls smoothly, with one lock shared by the menu and the enquiry form
- 05Counts its figures up as they scroll into view
- 06Takes project enquiries through a validated form in a focus-trapped dialog
- 07Scales every measurement from one root size, from 360 pixels to beyond 1920
How it was solved
- 01Built the reveal on a 2D canvas: the pointer's path is filled in with soft brush stamps and masked against the second image
- 02Tied the fade to real elapsed time, so the trail lasts the same on a 60 Hz laptop and a 120 Hz phone
- 03Read the picture's own position from the page so the canvas layer sits on it to the pixel
- 04Asked for the smallest image that still covers the canvas, and stopped the loop whenever the pointer rests
- 05Baked the world's land into about 2,700 dots at build time, then drew each shade of depth as a single path, so a full turn of the globe costs a handful of draw calls
- 06Redrew the globe only on a drag, a resize or a tick of its clock, never on a timer for its own sake
- 07Held the loader until the largest picture had loaded, with a ceiling so a slow network never traps the visitor
- 08Served pictures as AVIF and WebP at the size they are shown, with the hero fetched first
- 09Made the dialogs properly modal: focus is trapped, Escape closes, and the page behind is inert
- 10Honoured reduced motion everywhere, down to switching the reveal off
Stack
- Languages
- TypeScriptCSSHTML
- Front-end
- Next.js 16 (App Router)React 19TurbopackServer Actions
- Motion and graphics
- MotionLenisCanvas 2D
- Styling
- Tailwind CSS v4Design tokensnext/font
- Performance
- next/image (AVIF, WebP)Partial prefetchingCache Components
- Tools
- ESLintGitGitHub
- #nextjs
- #typescript
- #canvas
- #motion
- #tailwind
- #accessibility
The case study is the how. The site is the proof.