Release flyer assets
Blocked
Next action
Review blocker
Portfolio demo · sample data
Every blocked project, on one screen.
A work tracker that gathers whatever is waiting on a decision, shows you what's in the way, and names the one next action. No status meetings, no digging — just sample data you can poke at.
Sample data only No login Runs in your browser
Review
1 owner gap
3 work items need a decision
Q3 onboarding rewrite
Ready
Next action
Assign owner
Vendor contract review
Done
1
Next action per item
never a to-do pile
2
Engines, one contract
static demo and backend, identical
107
Button families click-tested
every build, in a real browser
0
Logins or installs
sample data, in your browser
The signature move
Where it is. What's blocking it. What to do next.
Every item reduces to three columns. If the next action is clear, the work moves — that's the whole discipline.
WhereRelease flyer assets
BlockerWaiting on the source folder audit
Next actionReview blocker, then hand to Print shop
How it behaves
Attention, not activity
Blocked work carries a warning border and rises to the top. Finished work fades out of the way, so the live decision stays loud.
One command per card
No checkbox soup. Each item offers the single next action, and taking it is a click — or a keystroke.
Every change leaves a receipt
Finish work, clear a blocker, add a note: each action states exactly what changed, right where you clicked. One click, or ⌘Z, puts it back.
Built to be checked
A demo that's wired to prove it holds up.
The interesting part of a portfolio piece isn't that it looks finished. It's whether it behaves, and this one is built to show its work.
Turnstile-gated
Cloudflare Turnstile verifies humans before the app loads. Protected assets require same-origin Referer.
Rate-limited & bot-blocked
Per-IP rate limiting via Durable Objects. Known AI crawlers are rejected at the edge.
Every button click-tested
CI drives a real browser that clicks every enabled control on every screen, and fails the build if one does nothing.
Two engines pinned together
Gate scripts assert the static demo and the backend produce the same workflow, on every push.
Byte-budgeted & sealed
Public files ship under size budgets, and the build fails if anything internal or oversized leaks out.
What this demo doesn't claim: real integrations, authentication, or production scale. It's sample data with no login, by design — a portfolio piece, not a product.