A portfolio that refuses to make things up

When I set out to build this portfolio, one rule sat above all the design and engineering decisions: nothing on it gets invented. No estimated metrics, no rounded-up outcomes, no clients or dates that have not been checked. If something is not verified, it does not appear.

That sounds like a content policy. It turned out to be an architectural one.

The temptation

Portfolios are full of numbers. "Increased conversion by 40%." "Served 2 million users." "Cut costs by a third." Some of those are true and carefully measured. Many are estimates that hardened into facts through repetition, or numbers with no stated baseline, period or method.

A sceptical reader — exactly the kind of senior person a portfolio is trying to persuade — discounts all of them, because they cannot tell which is which. An unsupported number does not just fail to persuade. It makes the supported ones less credible too.

How the rule shaped the build

Sections that hide themselves. The career timeline and the impact section only render when they have verified entries. With nothing verified, they are removed from the page and from the navigation, and the section numbering closes up so there is no visible gap. An empty "Impact" heading would be worse than no heading.

Draft by default. Every career entry, qualification and metric carries a status. New records start as drafts, and drafts never reach the public site. Publishing is a deliberate act.

Optional everything. A project's role, period, responsibilities and outcomes are all optional. The case study renders only the fields that have content, so filling one in later is purely additive. Nothing needs a placeholder to keep a layout from breaking.

Honest placeholders. Until a project has real screenshots, it shows a generated typographic plate — clearly an illustration, not a fake screen. Stock imagery that implied a product would have been its own kind of invention.

Tests that enforce it. An automated check confirms that no draft placeholder text ever appears on a public page. If the publishing gate ever breaks, the build says so.

What it costs

A site that refuses to invent looks less complete for a while. Some sections are missing. Some case studies are shorter than they could be. That is uncomfortable, and it is meant to be. The discomfort is the pressure to go and verify things properly, rather than to fill the gap with something plausible.

The broader point

This is the same principle that runs through the rest of my work: good systems are opinionated about the few things that matter. For a portfolio, what matters most is that a reader can trust what they read. Everything else — the motion, the typography, the architecture — exists to present true things well.

Anything I have not verified, you will not find here. What you do find, I can stand behind.