Vai al contenuto
Tutti i casi studio

Per ora questo caso studio è in inglese.

How I built this site

My 2023 portfolio was a hero, an About section and a CV that leaked my phone number. This is how I rebuilt it to feel like meeting me, in four languages, with every decision written down.

Ruolo
Design + frontend
Periodo
Nov 2026 — ongoing
Stack
Next.js 16 · TypeScript 7 · Tailwind 4

01 · Il problema

It didn’t sound like me

The old site was a template with my name on it: no projects, no story, a dark-mode button that did nothing, and a public CV with my birth date, phone number and home address.

02 · Vincoli

Four languages, 30-second readers

  • Recruiters skim: role, experience and CV must be visible right away
  • EN, PT, IT and DE: native in one, bilingual in another, still learning the other two
  • Free hosting and a free Figma plan (one mode, three pages, a tool-call quota)
  • No personal data in the repo, ever again

03 · Opzioni

Three ways forward

  • Patch v1

    Fast, but keeps every structural bug.

  • Astro

    Great for content, less overlap with my day job.

  • Scelta

    Next.js 16

    The stack I use at work, with server components and i18n routing built in.

04 · Decisione

Rebuild, and write it all down

“Every choice gets a log entry: context, options, decision, trade-offs. This page is written from that log.”
docs/case-study/decisions.md

05 · Risultato

What changed

  • 4languages, typed so a missing translation fails the build
  • 30+browser tests, incl. accessibility checks in every language and theme
  • 0photos with GPS or camera data; a test enforces it

The tests caught real bugs on the way: a theme button whose accessible name didn’t match its label, a notification that lost contrast in dark mode, and long German words overflowing on phones.

06 · Cosa ho imparato

Constraints are design input

Figma’s one-mode limit pushed me to name design tokens exactly like the CSS variables they became. When the Figma quota ran out, prototyping in HTML got me closer to the real thing, faster. And writing decisions down made them quicker, not slower.

Continua a leggere