Projects

Things I've built

Every entry here exists because I wanted to understand something specific, not because it looked good on a portfolio. Where a project taught me something interesting, I've said so.

001 — Active

DevDrift

This site, and the second version of the practice project that became it. Hand-written HTML and CSS with a small progressive enhancement layer on top. Light and dark themes from a single color-scheme declaration, fluid type via clamp(), and a navigation menu that works from the keyboard.

What it taught me: that most accessibility problems come from choosing the wrong element, not from missing ARIA. The original menu was a <div> that couldn't be operated without a mouse; swapping it for a real <button> fixed the behaviour, the focus handling and the announcement to screen readers all at once.

HTML CSS Vanilla JS Static hosting Accessibility

Visit the site

002 — In progress

Untitled

The next build. Still deciding on scope, which is the correct amount of planning at this stage.

What it should teach me: handling real data rather than hardcoded markup.

Building

How I pick

What counts as a project here

The bar is low on purpose. A thing counts if I didn't know how to build it before, and I can now explain the decisions in it. That rules out most tutorial output, which is fine — I still do the tutorials, I just don't get to claim them.

It also rules out pretending half-finished work is finished. Where something is broken or stalled, I've labelled it that way. A list of twelve completed-looking projects where three are real tells on myself more than a list of three real ones.

Elsewhere

The commit history is the longer version

Small, frequent commits with messages that explain the reasoning — including the ones where the reasoning was "this was broken."

See it on GitHub Get in touch