Turning My Portfolio Into a Living Arcade Surface

On June 13 I shipped the biggest change this site has had in a while: the portfolio stopped being a static resume page and became a living system. The visible pieces are playful, but the work underneath is practical. The homepage now has a Now Building panel, a Ship Log, a Skill Tree, a live Lab cabinet, a changelog timeline, and a shared arcade identity that can move between the portfolio and the lab.

Why this mattered

Personal sites go stale because every update feels like a small CMS chore. I wanted the site to have a place for recent work, a place for proof, and a place for experiments without turning every update into a redesign. The Ship Log solves the first problem. The GitHub heatmap and project links solve the second. The Lab cabinet solves the third.

The implementation shape

The portfolio keeps the editorial content in small data files. The arcade surfaces read from those files instead of hardcoded JSX, so updating what I am shipping is now a content change. The Lab runs as a separate site, but embedded apps can report their height back to the portfolio and accept language/theme parameters. That keeps the main page polished while the experiments remain independently deployable.

The real lesson

The lesson was not gamification for its own sake. It was about creating maintenance paths that I will actually use. If the site makes it easy to add a ship, update the now panel, and point to a real project, the public profile stays alive. If it takes a redesign, it will drift again.