A portfolio site built to be read rather than scrolled past.

The brief I set myself: most developer portfolios list technologies and hope the reader assembles a picture. I wanted one that makes a claim and then proves it.

Type. A single oversized editorial headline carries the whole hero — "I build systems that turn signal into something you can act on." Set tight, three lines, with two words picked out in colour so the eye lands on the claim rather than reading it as a paragraph. Body copy drops to a quiet grey at a comfortable measure, so the contrast between claim and evidence is structural rather than decorative.

Colour. Near-black base at #0A0E1C so the two accents do all the work — teal for the claim, amber for emphasis and the primary action. Two accents, one job each. Nothing else competes.

Structure. Work with me, then Experience, then Projects, then Skills. Ordered as a conversation: what I can do for you, proof I've done it, the artefacts, then the detail. Project cards separate overview from stack from contribution, so a non-technical reader and a technical one can each find their layer.

Honesty as a design constraint. Projects are labelled by what you can actually inspect versus what is only listed. Three you can open, two stated plainly. That constraint shaped the card design.

Designed and built end to end: type scale, colour system, layout and copy, then hand-written HTML and CSS with no framework overhead. Deployed on GitHub Pages.