DM-01 · Projects · REV 2026.11
PRJ-003Live
DomDev Portfolio
This website — a minimal static portfolio with a live terminal in the hero, MDX case studies and GitHub integration.
- platform
- Next.js
- lang
- TypeScript, CSS
- duration
- 3 weeks
- year
- 2026
- type
- web
- code
- 9,000 lines
- authors
- 1
Next.js · TypeScript · Tailwind CSS · MDX
Overview
DomDev is my personal portfolio — but it's also a project in its own right. The goal was to build something that feels like a product landing page (Linear, Vercel, Stripe) rather than a template portfolio, while staying fast, accessible and easy to maintain.
Problem Statement
Most student portfolios are static template sites that all look the same. I wanted a site that demonstrates real engineering: 3D graphics, a typed content pipeline, API integrations and attention to performance — something a recruiter remembers after closing the tab.
Solution
A Next.js App Router application where every piece of content lives in a typed content layer (zod-validated data files and MDX), rendered through a small custom design system. The centerpiece is a WebGL globe built with React Three Fiber that reacts to scroll and mouse movement.
Features
- Interactive 3D globe hero with connection arcs, particles and an atmosphere shader
- Command palette (Ctrl+K) with fuzzy search over every page, project and post
- Built-in terminal with real commands and hidden easter eggs
- Recruiter Mode — a condensed 5-minute view of the whole site
- Live GitHub integration: repos, languages, contribution calendar
- MDX-driven project case studies and blog
Technical Implementation
The globe renders ~2,500 instanced points distributed on a sphere with great-circle arcs drawn between visited countries. Scroll progress from Framer Motion's useScroll drives opacity and scale; a ref passed into the R3F canvas lets useFrame lerp rotation without jitter. Pointer position is smoothed into a group tilt so the motion feels weighted rather than twitchy.
Content is validated at build time: every skill, experience entry and MDX frontmatter block passes through a zod schema, so a typo in a data file fails the build instead of silently rendering broken UI.
Challenges
- Keeping the WebGL scene at 60 fps on mobile meant capping device pixel ratio, instancing all particles and pausing the render loop when the hero scrolls out of view.
- The cinematic hero transition required coordinating scroll-linked Framer Motion transforms with the Three.js render loop — the fix was writing scroll targets to refs instead of setting rotation in scroll handlers.
Lessons Learned
- Design tokens first, components second — retrofitting a theme is far more painful than starting with CSS variables.
prefers-reduced-motionis not an afterthought; building the static fallback early made every animation decision cleaner.
Future Improvements
- AI chatbot trained on the site's content layer
- Public visitor analytics dashboard
- Localized versions (English + German)