For a long time my portfolio was a grid of screenshots. The problem: most of the sites I build move. A loader, a scroll-driven hero, a checkout flow. A screenshot shows none of that.

So I rebuilt it with one rule: every project is told part by part, and every part has a video of the real site working.

What's in it

  • A home page with an introduction and a wheel of projects you move through by scrolling.
  • A projects page grouped by type: e-commerce, landing pages and portfolios.
  • A case study for each project: the problem, what was built, the decisions and the outcome, each part with its own video.
  • An identity page with the logos and brand pieces I designed for clients.
  • An about page with technologies, education and GitHub activity refreshed on every build.
  • Three languages, light and dark mode, and a contact form with no backend of its own.

Each project, part by part

Three decisions

1. Why walk through each project part by part?

Because a screenshot doesn't show an animation or a checkout. Each part has a video of the production site next to the text that explains that decision. And if the visitor prefers less motion (prefers-reduced-motion), they get a still image instead of the video.

Recording those videos was its own small project. Real-time screen capture stuttered on my machine, so I ended up recording frame by frame with Playwright and a virtual clock injected into the page, which gives perfectly smooth video no matter how slow the computer is.

2. Why a page just for identity?

On several projects I also designed the brand. Putting logos, variants and graphic pieces together in one place shows that work without mixing it with the development.

The identity page

3. Why three languages and two themes on a personal site?

Because different people read it: local clients and teams abroad. All the copy lives in translation files, with parity between languages checked by tests, and the theme switches with one tap.

Result

The portfolio is live, the code is public on GitHub, and automated tests and checks run on every change. It's where I add each new project, and it's also the best sample of how I work.

Stack: React, TypeScript, Vite, Tailwind, GSAP, i18next, Vitest.

Feedback is very welcome, especially on the case study format.