Work

Run PSL: a complete build, in the open

Before asking anyone to pay for this process, I ran it end to end on a real public website of my own. Everything about it — the code, the history, the checks, the deployments — is open for inspection.

Owned demonstration projectNot commissioned client workLive and publicly verifiable
Read this first

What this is, and what it isn't

Run PSL is my own community project — a free directory of running events, group runs, routes, and resources around Port St. Lucie. Nobody commissioned it and it has no business metrics to brag about. I built it to demonstrate, honestly, that I can take a website from nothing to a live, maintained, professionally delivered product. Judge the craft, not invented results.

The build

What was delivered

Researched content
Every listing is backed by a public source and carries a verification date — a discipline enforced by automated tests.
Mobile-first design
Built for runners checking a phone, with automated tests confirming the layout holds on small screens.
Accessibility & security basics
Keyboard navigation, skip links, focus states, and strict browser security headers.
Fast static delivery
No trackers, no third-party scripts, hosted on Cloudflare's global network.
Screenshot of the Run PSL homepage showing its directory of local running events

The delivery pipeline

How it was shipped — the part that matters to you

This is the same pipeline your project would use. Each piece exists so problems get caught before your customers ever see them.

  1. Version-controlled from the first line

    The full history of every change lives in a public GitHub repository — who changed what, when, and why.

  2. Automated checks on every change

    Each update runs a battery of automated tests — build integrity, HTML validity, content rules, and real-browser checks on desktop and mobile — before it can ship.

  3. Preview before production

    Changes deploy first to a private preview URL for review — the same mechanism clients use to watch their site take shape.

  4. Rollback, rehearsed

    I deliberately shipped a change and then reverted it through the same reviewed process, proving that if something ever goes wrong in production, it can be undone quickly and cleanly.

Want this level of care on your site?

Your project gets the same pipeline, plus the founding-client rate while it lasts.