A new portfolio, designed by me and built with an AI agent.

Before writing a line, I wrote the rules. In a chat with Claude I set down positioning, audience, the three arguments to make (systems that last, design driven by research and data, a hybrid profile between design and code), the site map and the copy for every section.

The document becomes the single source of truth: the agent reads it first, and where a decision is still open it has to ask, not invent. Placeholders stay in square brackets until I have real data.

The real work is a short loop. I ask for a change, look at it in the browser, then correct or approve it.

In a single evening there are 43 commits: logo, header, footer, archive, menu, CV page. Each commit is a small, reversible decision.

The agent proposes, but design judgement can't be delegated. I often had to course-correct: on vocabulary, on readability, on how information was cut. Sometimes the agent wandered off, added more than needed or over-explained, and the job was to bring it back to the essentials.

• The logo. The original file no longer existed: it was rebuilt as a vector from the old png. I had it corrected until the letters matched the original script.
• The Home opening. An early spec called for mentioning my path at Telepass and Dst right away. I went for a full-screen opening with more context, with my first and last name as the headline.
• Telling the Telepass story. The initial mapping had a parent page and five chapters. Once built, it felt too fragmented: it became a single page with four moments and an index that follows the scroll.
• Accessibility. Minimum contrast fixed on years and labels where the grey was too light.

The technical decisions were weighed against the systems already in use, with a touch of innovation:

• Hosting. Netlify was set aside because on the free plan the site would stop once credits ran out; the existing Aruba FTP would have required authorising the IP address every time. The choice fell on GitHub Pages: free, and every commit is published automatically.
• Domain and email. They stay on Aruba: I only changed the website records, without touching the email ones.
• HTTPS. The certificate wouldn't issue: Aruba's DNS servers weren't in sync yet. We waited, then forced a new request.
• Privacy. Google Analytics only starts after consent, with Signals and advertising data switched off in the code.

A portfolio site without measurement is an opinion. With the agent I wrote a script that reads Google Analytics data every week and produces a short report: 5 numbers, 3 observations, 1 suggestion.

First week online: 39 visitors, almost a minute and a half each, the Telepass page read past 90% by 10 people. LinkedIn is the channel that brings the most visits after direct links. The data also showed what was missing: email clicks weren't being counted, so I added them.