How this page is built

We make hardware do more with less. The site is built the same way.

WHAT IT IS

Plain files. One page, one script, one stylesheet. No framework and no build step.
One library. The 3D is drawn with a copy of three.js that lives in the site. Nothing else is loaded but two fonts.
About three quarters of a megabyte, all in. The script we wrote is 36 KB. The two data files are 60 KB together.
It runs on your graphics card. The tower is 24,576 points and the field is 4,923, each drawn in a single pass by a small program on the GPU. Nothing is updated point by point in script.

One number drives everything. Your scroll position becomes a single value, and every position, size and colour in the scene is calculated from it. That is why scrolling back replays it in reverse.
Points stay crisp. Each point is sized in screen pixels with a floor and has a soft edge, so a dense grid never flickers or bands, on a phone or a wall display.
The crowd is packed like a sunflower. Teams with the same score sit in a disc, each one a fixed golden angle on from the last, which fills the disc evenly.

The 8,208 points that fall out of the tower are the experts we actually removed, layer by layer.
The 4,923 dots are every team's final score, and our climb is drawn from the leaderboard as it was recorded.

If you have asked your device for less motion, the idle movement stops and the scene changes only when you scroll.
If your browser cannot draw 3D, you get every word over a plain background.
Nothing on the page is set smaller than 14 pixels. Keys 1 to 7 jump between chapters.