Aconite
ongoingThis site, built like a product instead of a resume.
Why it exists
A list of job titles does not show how I think. I built Aconite so each project can be told properly, with the reasoning behind it, and so the site itself is evidence of how I work: typed, validated before it ships, and hardened by default.
Features
Case studies, not bullet points
Each project gets a full page with its purpose, my role, and what I actually worked on. Not a line on a CV.
Content checked before it ships
Every project is validated against a strict schema at build time, so a broken entry or an unsafe link fails the build instead of reaching a visitor.
Hardened and fast by default
Static delivery, zero client-side JavaScript, and a strict content security policy keep the site quick to load and safe to host.
Why I built it
I wanted a place to explain the things I have built without flattening them into a few lines on a resume. Each project comes down to the thinking behind it: what problem it solves, the decisions I made, and why. A static site felt right because the content is the point, and I did not want anything between a reader and the writeup.
What I worked on
The build was done with AI tools. What I set was the standard: the site should hold itself to the same discipline as the products it describes. Every project entry is validated against a strict schema before the site ships, external links are checked, and the whole thing renders to static HTML with no client-side JavaScript. Keeping scope tight and the rules enforced took real effort. It is a small site, built the way I would want any product built.