TYRIEN JONES AI ENGINEER · FOREMAN
THE WORK SAMPLE

How this site is built

You’re looking at the work sample. This page is how it’s made — and how I made sure every word on it was true before it went up.

FRAMEWORKNone
BUILD STEPNone
JAVASCRIPTNone
TRACKERSNone
HOSTINGCloudflare Pages
TLS AUTO-RENEWS
00 · THE BUILD

A plain static site — hand-written HTML and CSS, no framework, no build step, and no JavaScript at all.

The menu is plain links, so there’s no script to switch off. One shared stylesheet drives every page, so adding a new page is copy one file and add one link.

WHAT LOADS
From this address
Everything
Analytics · trackers
None
Cookies
None
Type
System fonts or font files I host myself
Icons
None. The arrows are plain text
Access
Keyboard-navigable, respects “reduce motion”

Don’t take my word for any of it — hit “view source.” What you see is what there is.

01

The result

I built it to run anywhere, and it does. It started self-hosted on hardware I control, behind locked-down security headers and a strict content policy, and scored an SSL Labs A+. I did that to prove I could. Then I moved it to Cloudflare Pages: same files, nothing rewritten, the security certificate renews itself, and an update is one push to GitHub.

The same strict security headers and content policy now ship from a plain headers file in the repo, so anyone can read exactly what the site sends.

Fast, private, and boring on purpose. Nothing fragile, nothing to break, nothing phoning home.

02

How I ran it

Same way I run everything: the AI did the typing, I did the directing — designed, checked, and signed off by me. Then I did the part most people skip.

INDEPENDENT FACT-CHECK · BEFORE GO-LIVE · RE-RUN NOV 2026 Fresh, read-only AI agents — one per project — checked every claim, version number, and count against what’s really on disk.
Stale numberscaught
One oversella “tested” without the tests
A couple of undersellsfixed too
Nine months on, I ran it again before rewriting these pages. Every number here was re-checked against the real repos.

Nothing here is dressed up, because it was checked.

03

What I don’t publish

The setup behind my own tools — the machines, the network, how they connect — I deliberately keep off the public internet. Posting your own infrastructure is how people get themselves hacked. It’s the same judgment I’d bring to your systems. Happy to walk you through the whole architecture in an interview.

WORK WITH ME That’s the site, and that’s how I work.
LET’S TALK ABOUT THE JOB →