How this site
is built
The portfolio is its own case study. Open the engine readout at the bottom right to watch the renderer work.
The rendering pipeline
Every word is static HTML; the 3D layer reads one shared scroll state.
Six decisions
Every word is static HTML
Googlebot does not support WebGL and the AI crawlers measured so far do not run JavaScript. So Next.js prerenders every route, and the 3D scene is decoration behind the text, never the text itself.
One renderer for WebGPU and WebGL 2
three.js WebGPURenderer uses WebGPU where the browser has it and its own WebGL 2 backend elsewhere. If the WebGPU device is lost, the site swaps in a fresh canvas on WebGL 2 and remembers that for the visit.
3,800 instances, a handful of draws
Every chapter re-forms the same 2,400-block instanced mesh, and 1,400 particles share a second one. Each frame is one pass over preallocated typed arrays, skipped entirely once the blocks settle. The bloom passes add a few more draws; the engine readout shows the live count.
The DOM owns scroll; the GPU only reads
Sections declare their formation in HTML attributes. One ScrollTrigger maps scroll to formations and writes four numbers into a shared object; the render loop reads them. React never re-renders per frame.
Motion is optional everywhere
The operating system's reduced motion setting is the default, and a Pause motion control overrides it. With motion off there is no smoothing, no reveal, no intro, and the scene snaps instead of travelling.
Degrade in order
WebGPU, then WebGL 2, then no scene. Motion on, then off. JavaScript on, then off. Each step keeps every word and every link.
The performance budget
Text paints first
The hero headline is server HTML and paints immediately, even behind the intro, so it stays the Largest Contentful Paint.
3D loads late
three.js is its own chunk, fetched when the browser is idle after the page is interactive.
Pixel ratio cap
2 on desktops, 1.5 on phones and machines with four cores or fewer.
Bloom only where it is cheap
Phones and machines with four cores or fewer skip the bloom pass.
Idle when hidden
No frames while the tab is hidden or a paper section covers the screen.
Skipped on low memory
Data saver and very low memory devices get the page without the scene.
Built with
Next.js 16 · React 19 · TypeScript · Tailwind CSS 4 · three.js r187 WebGPURenderer and TSL · GSAP ScrollTrigger · Lenis · Vitest
The research, the architecture decision records and the reviews behind every choice are in the repository’s docs folder.