luke b

project detail

this portfolio

a personal portfolio app that started as a simple static site and grew into a multilingual, data-backed space with live activity, changelogs, analytics, guestbook entries, private status tooling, and a growing set of hidden pages.

apr 2026html, css, vanilla js, vercel api routes, supabase, spotify, github, cloudflarelive

what it is

my personal site, but treated more like a small app than a static brochure. it now combines hand-built pages with live api-backed sections for activity, music, guestbook posts, build metadata, commit logs, analytics, and private status management.

what it had to do

stay fast and readable while scaling beyond a basic portfolio. that meant adding dynamic features, multilingual routing, admin tooling, and hidden routes without losing the low-friction editing workflow or making the site feel generic.

who it's for

recruiters, other developers, and anyone who wants a fast overview of what i build without waiting through a bloated site.

key features

  • locale-aware routing and translation support across the site, with shared runtime handling for localized pages.
  • live sections powered by small vercel api routes, including now-playing, current activity, changelogs, commit heatmaps, build metadata, and page analytics.
  • supabase-backed guestbook, page view tracking, event analytics, and private status data for the public now page and the private admin flow.
  • custom runtime polish like animated ambient backgrounds, footer build tooltips, smooth locale loading, and lightweight client-side enhancements instead of a framework-heavy app shell.
  • hidden and personal routes, private pages, and small easter-egg style touches so the site feels authored rather than templated.

what i built

i built the design system, page structure, content architecture, translations, shared runtime behaviour, analytics plumbing, guestbook flow, changelog and commit views, spotify integration, private status endpoints, and the small admin surfaces that let me keep the public pages current.

result

the portfolio now works as a lightweight personal platform instead of a static landing page. i can ship updates quickly, log changes properly, surface live data, maintain multilingual versions, and keep adding new sections without throwing away the simplicity that made the site easy to own in the first place.