Building this site as a project

Context

In this job search moment, I needed something differentiated. Traditional CVs aren't accepted in person due to data protection policies. I needed an alternative way to reach people. I also wanted an archive for my photography. This project combined both needs: a presentation for recruiters and a space for projects, work experience, and visual work.

Project framing

I treated this site as a standalone project with clear goals. Create an alternative to a traditional CV. Centralize projects and photography in one place. Keep it minimal and editorial. Ship it fast without compromising quality.

The challenge was execution speed. I don't have the technical knowledge to build a functional site in 72 hours on my own. That's where tool choice became critical.

Strategy & decisions

I chose Manus as the execution platform. The reason was simple: speed, iteration capacity, and low technical overhead. I could focus on information architecture, copy clarity, and visual restraint instead of wrestling with code.

Key decisions. Information architecture first. Define structure before design. Pages, sections, navigation, and content hierarchy came before aesthetics. Copy clarity. Every sentence needed to serve a purpose. No filler, no buzzwords. Visual restraint. Editorial typography, grayscale photography, minimal UI. Let the content speak. Scope discipline. Included only what was necessary for a recruiter to evaluate me.

Execution data

Outcome

The site is live, functional, and recruiter ready. It serves as both a portfolio and a working document I can update as I ship new projects or refine existing content.

It's another example of planning, execution, and delivery under constraint. I identified a need, framed it as a project, made strategic decisions, and shipped a working solution in 72 hours.

This project also gave me the opportunity to test a new tool. Based on the result, Manus is now part of my toolbox.