Classic version
Case 4 · This portfolio
How I built this portfolio with AI
A few design decisions and quite a bit of trial and error.
My starting point
My previous portfolio lived in Notion. It was pretty simple, it was out of date and, although it did its job, I felt I could do more.
Before
Notion
A simple, outdated portfolio.
Now
My own website, built with code
And a repository to understand how it works.
I could have updated it and left it at that, but I wanted to challenge myself.
I wanted to try building my own website with code, understand how a repository worked and learn a bit more about everything that usually stays on the other side of Figma.
And, while I was at it, rethink how I was telling the story of my projects.
V1Two ways of telling the same story
My first idea was to let each person choose how to read the cases.
On one side, a “classic version”, with the structure we usually find in portfolios: problem, process, decisions and results.
On the other, a “gossip version”, more conversational, with behind-the-scenes stories and a narrative much closer to the way I tell things.
Gossip version
I loved the idea; it felt like a fun way to do something different.
But then came the first reviews and the feedback.
V2Less back-and-forth, more clarity
Having two versions doubled the content and made reading harder. On top of that, the cases were really long.
I wanted to say so much that what mattered got lost among all those paragraphs, so I decided to simplify.
I kept a single version that combined the best of both: the clarity and structure of a case study, but in my voice, without so much formality and without telling absolutely everything that happened.
Classic version
Gossip version
A single version
- The clarity and structure of a case study
- In my voice, without so much formality
- Without telling absolutely everything that happened
In the end, I didn’t need two versions to tell better stories about my projects; I needed to learn to edit just one.
And that’s how I got to what you’re reading now.
I’m not a developer, but I didn’t want that to be a limit either
I decided to build the site with Claude Code, an AI tool that helped me turn my ideas into code.
My way of working was to translate my design decisions into clear, detailed prompts.
What I defined in each prompt
- The goal of each section
- The information hierarchy
- The components
- The interactions
- How to adapt to different devices
Then I reviewed the result in the browser (I worked on everything locally first) and identified what worked, what didn’t and what needed adjusting.
Claude Code wrote the code, but my design knowledge was what guided the instructions and the decisions.
What’s behind what you see
- 01AstroTo build a lightweight site.
- 02Graphics in codeAdaptable to different screens.
- 03Reusable componentsFollowing a logic similar to a Design System.
- 04Mobile-first designDesigned for phones from the start.
- 05AccessibilityAlt text and animations that respect the reduced-motion preference.
- 06Git and GitHubTo version the project and keep a record of changes.