← Work

Case 16 · Live

KodeKid — a portfolio you're allowed to break

Most portfolio sites are a grid of screenshots you scroll past. This one turns its own tagline — Think it. Make it. Break it. — into something you can play with: the logo builds itself as you scroll, every case moves, and if you know where to tap, every letter on the page becomes a brick you can smash.

Watch the video

Role: Concept, Design and Development · Own site · 2026

The problem

A portfolio is supposed to show what you can do. Most of them show it in the least convincing way possible: a static grid of screenshots, a paragraph per project, a contact link at the bottom. Nothing on the page itself demonstrates the craft it describes. If the work is creative coding, the site has to be creative coding — otherwise it's just a brochure about it.

The idea

KodeKid runs on three words: Think it. Make it. Break it. Instead of parking them under a logo and moving on, the whole site is built as the tagline in action.

Think it. The front page opens with the logo in pieces. Scroll, and the letters find each other and lock into place — then the page flies straight through them and the tagline takes over.

Make it. The work isn't shown as screenshots. Every case plays as a silent six-second loop, the work section fades in from dark, and "Surprise me" deals you a random case instead of making you pick from a list.

Break it. Literally. Stay on the front page for 30 seconds and a ladybug wanders in — catch it, and every piece of text comes unstuck and falls to the floor. Tap five times, or type the Konami code, and the page becomes Breakout: every letter a brick. Either way, the page puts itself back together afterwards.

The decisions

Play only works if the foundation doesn't wobble. A page you're invited to break has to be solid enough that breaking it feels like a game, not a bug — so the playful layer sits on top of a site built to the same standard as any client job: Next.js on Vercel, content from Supabase, structured data on every page, and accessibility treated as a requirement rather than a score to chase. The numbers, including the one weak spot, are on Behind the site.

The easter eggs are hidden, not mandatory. Someone who just wants to see the work and send an email can do exactly that without being dragged through a game. Someone curious finds more — and because a hidden thing only matters if someone finds it, there's a page that tells you where they are.

Adding a case had to take minutes, not a deploy. So there's a custom admin behind the site: a case is written in markdown, a screen recording is uploaded, and the front-page loop and the poster frame are made from that recording right there in the admin.

What was built

A bilingual site (English and Danish) with a scroll-driven front page where the logo assembles itself and the tagline takes over, a work section with a random case picker, category filters and moving loops instead of screenshots, two playable easter eggs built from the page's own content, and a custom admin that turns a markdown text and a screen recording into a finished case. Underneath: 100 on accessibility, best practices and SEO in Lighthouse on desktop.

Result

Live at kodekid.app — you're on it. Go back to the front page and break something. It'll put itself back together.

Same hands, running products

This site isn't the only proof. I'm the founder, designer and developer behind Klokly — a time-tracking SaaS running in production — and TekstFox, an app for SMS automation. Both are built to the same standard as this site, and both have their own case here: the Klokly case and the TekstFox case.

kodekid.app

ENDA