July 16, 20264 min read

How I built this site: using AI as a method

An editorial design system, an intentionally lean build, and AI used as a working method—with the decisions staying in human hands.

I set one rule while building this portfolio: every decision needed a reason. Colour, type, space, and motion could not exist simply because a template put them there. Here is the short version of how the site came together.

System first, pages second

I began with a visual contract: an ivory surface, charcoal text, one coral accent, and measured use of cobalt. Headings use a condensed display face; body copy stays calm and readable. Corners have no radius, and motion is limited to three timing ranges. Once those rules were clear, every page began to speak the same language. To me, that consistency matters as much as any individual composition.

Editorial system diagram showing colour, typography, grid, and components forming a complete web page — 01 / SYSTEMThe rules came before the pages.Colour, type, spacing, and component decisions became one shared visual contract.

AI is a tool; the decision is human

I used AI as a way to accelerate the process: first drafts, alternative layouts, and accessibility copy suggestions. I did not accept any of them untouched. I chose which composition worked, which sentence stayed, and whether the contrast was sufficient. The tool proposes; selection and responsibility remain with me.

Editorial collage showing a human selecting and refining one design from many generated layout options — 02 / DECISIONThe tool produced options; I chose the direction.Alternatives added speed, while filtering, editing, and the final call remained human responsibilities.

Fewer dependencies, more attention

I built the site without adding a runtime dependency beyond the framework. It was deliberate: fewer moving parts, faster pages, and simpler maintenance. Accessibility and performance were not polish saved for the end; they were criteria from the beginning.

Technical editorial diagram showing a web architecture with a small number of strong layers and unnecessary parts left outside — 03 / BUILDFewer parts made every responsibility more visible.Content, interface, and accessibility sit in a lean structure, with unnecessary runtime weight kept outside.

This is a starting point. As the work grows, I will keep sharing what real projects teach me and the decisions I make where design and development meet.