I Rebuilt My Personal Site as a DDR Song Wheel
My new site, space.la, lists every project I've shipped since 1997, and it's played like a dance game. It opens on a title screen. The logo slams down, PRESS START blinks on the beat and featured projects roll past like
My new site, space.la, lists every project I've shipped since 1997, and it's played like a dance game.
It opens on a title screen. The logo slams down, PRESS START blinks on the beat and featured projects roll past like an arcade attract loop. Press any key and you're in a mode select, then a song wheel where every project is a "song" with a BPM, a difficulty rating, a groove radar and a letter grade. My resume is a nonstop course.
This post is about why I built it this way, how it's put together, and how it still works as a fast, accessible website underneath.
Why DDR?
A personal site with decades of projects runs into the same problem every time. A list is boring, and a grid of cards all look the same. I wanted something you'd want to scroll through.
The DDR music-select screen solves exactly that. It's a menu built for browsing hundreds of entries, where each entry carries just enough at-a-glance data to compare and pick. It's also loud, neon and fun. A song wheel is just a catalogue with good taste in UI.
So space.la borrows DDR's menus, not its gameplay. There are no arrows to step on. It's the part of the arcade cabinet you'd spend ten minutes in picking a song.
The screens
Each screen maps a piece of the site onto a piece of the arcade:
- Title / attract mode. The logo, PRESS START, and a reel of featured projects. Your first key or tap also unlocks audio.
-
Mode select. Big tilted tiles, in the style of DDR Hottest Party:
- Free Play: every project, 1997 to now.
- Nonstop Course: the resume.
- Player Data: the About page.
- Bonus Content: the blog archive.
- Music select (the song wheel). Projects grouped into folders that open in place, like DDR. The side panel shows the selected project's jacket, a BPM readout, a foot meter, a groove radar, a grade and a score.
- Stage. One project per stage, with the full write-up.
- Nonstop Course. The resume plays one job per stage and ends with NONSTOP COURSE CLEAR! and a results screen.
- Player Data. The About page, styled as an e-amusement profile card with a skills radar.
Turning projects into charts
The fun part was deciding what a project's "chart" means. Every project gets the stats a DDR song has, computed from real data:
- Groove radar. Five axes: Stream, Voltage, Air, Freeze and Chaos. Each is a percentile rank across the whole catalogue, built from things like activity over time, stars, releases and published packages, how long the project lived, and how many languages and tags it spans. A long-lived, many-language project has a very different shape from a weekend hack.
- BPM. I set it by hand for projects I care about (Tish is 174, which feels right). Otherwise it's derived from how "hot" the project is.
- Foot rating. 1 to 10.
- Grade. Shipped projects are SS, active ones S, works in progress A and archived ones B. Featured projects get SSS.
Choosing which signals feed which radar axis turned out to be a real design exercise in summarising a body of work.
Every sound is synthesized
There are no audio files on the site. Everything you hear is generated live in the browser:
- UI sound effects for moving, selecting and going back.
- A procedural preview loop for every project, the way the song wheel plays a preview of the highlighted song. Each loop is seeded by the project's id, plays at that project's BPM and uses a musical key chosen by the project's family. Scroll the wheel and the music changes under you.
- A shared BPM clock, so pulses and blinks across every screen land on the beat.
Mute is remembered, and audio only starts after your first interaction.
WebGPU on top, real HTML underneath
The thing I cared about most: it's still a website.
- Every route is real, prerendered HTML. Search engines, screen readers and browsers without WebGPU all get proper pages with proper links.
- Then one persistent WebGPU island takes over the screen. It renders an HDR scene with dual-filter bloom and a starfield, and draws text from a glyph atlas.
-
Navigation stays inside the game. The game's router swaps the page content with
pushState, so moving between screens never reloads the page, and every screen still has a real URL you can share. - It adapts to the device. Quality drops automatically on slow devices.
- Without WebGPU, the HTML title page itself becomes the menu.
Input is what you'd want from a cabinet or a couch: arrow keys or WASD with DDR-style accelerating hold-repeat, a gamepad, the mouse wheel, or touch with drag, fling and tap on phones.
The look is pure StepMania theme: hot pink, yellow and cyan on near-black, skewed header plates, chevron strips and bloom everywhere.
Built on my own stack
space.la runs on Orbit, a web framework I built for it, and Orbit is written in Tish, the language I've been building.
Orbit handles everything around the game. It prerenders the static pages, regenerates the live project timeline on a schedule, streams search results from the server, generates feeds and SEO tags, and builds the CSS. The WebGPU game is a single Orbit island. I'll write up Orbit and Tish in their own post.
Go play it
👉 space.la: press start, pick a mode, spin the wheel.
Built with Orbit (github.com/tishlang/orbit) and Tish (tishlang.com).
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.