Case study · 09 / 12
Nova Adeyemi
Concept site for a fictional display pilot
- Year
- 2026
- Focus
- Three.js
- Status
- Live
A design concept: the website of an aerobatic display pilot who does not exist. Nine pages, a 3D helmet built entirely in code, and an animation engine written from scratch.
I set myself a brief with nowhere to hide: invent a pilot, then build her the site a real one would envy. Everything had to be made. The helmet is not a bought model. I wrote its geometry in code, ray-traced its shadows at build time and compressed it to under 700 KB. The studio lighting is code too. The hero is a portrait whose helmet burns away as you watch, and the cursor paints it back. Scroll on, and the page passes through her visor into the season map, then banks over a horizon into her career. To keep it all light, I wrote the animation engine myself, with one clock and no dependencies, and kept the 3D code out of the first download.
What it does
- 01Opens on a WebGL portrait whose helmet burns away, and returns under the cursor
- 02Passes through the visor into a dotted world map of a 14-stop tour
- 03Banks over a horizon into a career timeline with moving plates
- 04Lets you turn the full 3D helmet by hand in the Hangar
- 05Offers the next display as a calendar file, and a press kit as a PDF
- 06Runs to nine static pages, from a journal to a store front
How it was solved
- 01Modelled the helmet in code and compressed it with Draco: 115,476 triangles in a 694 KB file, with shadows ray-traced at build time
- 02Built the studio lights in code and filtered them at run time, so no lighting file is downloaded
- 03Wrote a dependency-free animation engine: one shared clock, springs, tweens, text splitting and scroll triggers
- 04Placed the visor window where the 3D scene projects it, so it lands on her eyes at every screen size
- 05Ran the scroll seams inside the smooth-scroll step itself, which took late frames from 3 in 11 down to none
- 06Rendered the sections on the server and loaded the 3D engine in one small island, so three.js stays out of the first bundle
- 07Graded the picture by device: resolution capped per class, 60 frames a second off desktop, and a still frame for reduced motion or data saver
- 08Prepared the portrait's depth and normal maps on my own machine, so the photograph was never uploaded anywhere
- 09Made zero third-party requests: every font, decoder and script comes from the site's own origin, under a strict content policy
- 10Drew the map from 9,649 land dots on an equal-area projection
Lighthouse 100 for accessibility, best practices and SEO on all nine pages, on phone and desktop. Under a throttled mobile connection the home page paints its largest element in 1.94 seconds with no layout shift.
Stack
- Languages
- TypeScript (strict)GLSLPythonCSSHTML
- Front-end
- Next.js 16 (App Router)React 19Static generation
- 3D and graphics
- three.jsCustom GLSL shadersMeshPhysicalMaterialglTFDraco compressionWebGL
- Motion
- Custom animation engineLenis
- Styling
- CSS with design tokensnext/font (Oswald, Space Grotesk)
- Testing
- VitestjsdomV8 coveragePlaywright
- Asset pipeline
- Node.jsdraco3dCustom BVH ray tracerPillowNumPySciPyShapelyONNX Runtime
- Tools
- ESLintGitGitHub
- #threejs
- #webgl
- #glsl
- #nextjs
- #typescript
- #concept
The case study is the how. The site is the proof.