Sketchby handPreview18 versionsFramesboardMy marksby tagBuildthe next roundSite repoprivateCloudflarePagesLivedafspace.comNothing about the look was built before I marked it

Systems · 2026

This site, from a sketch to 1.0

My own portfolio, directed rather than coded. A hand sketch on Nov 14, eighteen private previews and a board of real screenshots I marked by tag, then my own domain and a 1.0 that went live on Nov 19.

Role
Owner and art director
Built with
Claude Code and one Python script, no framework
Iterations
18 private previews, 24 versions of the frames board
Hosting
a private GitHub repository, Cloudflare Pages on the free plan
Domain
dafspace.com, bought at Porkbun
Timeline
brief on Nov 14, live on Nov 19, 2026
Nov 14: the first frames from my sketch

The problem

My work sat in pieces: LinkedIn, a resume, and the records of two years at Worksport. My one earlier attempt at a portfolio site had stalled. I wanted one place that shows the work as it is, with real numbers and real photos, that I can change and publish without hiring a developer.

The frames board, where every change was marked

The decision

Direct it instead of coding it. Claude Code builds the site from plain text drafts with one script. I sketched the first screen by hand, and from then on every change to the look went through a board of real screenshots of the built site. I marked a frame, Claude built only what I marked, and nothing went public until I said so.

A tag for every part, so a change takes three words

Why it works

Marking real screenshots kept each round short. The two open layout choices were settled on the board as 1A and 2A, a solid red title box was turned down within the hour, and the phone header was measured to the pixel rather than judged by eye. Once every part had a tag (H1 for the title box, C3 for a card's line, and so on), a change could be asked for in three words.

The hosting is written down in one runbook: every setting, what it costs and how to rebuild it from nothing. A rebuild from the repository alone matched the live site exactly, so I can change, roll back or move it without anyone else.

From a sketch to dafspace.com
Sketchby handPreview18 versionsFramesboardMy marksby tagBuildthe next roundSite repoprivateCloudflarePagesLivedafspace.comNothing about the look was built before I marked it

The design rounds

Nov 14

The first frames

The main screen from my sketch: a title box with my name, three tabs hanging under it and a rolling list of cards, white with red. The Production tab opened lit.

Nov 14 to 20

The frames board

Every look change went through this board: real screenshots in rows, a note under each, A and B choices side by side. I picked 1A (project pages open with the large header) and 2A (the tabs sit at the right of the small bar).

Nov 19

Marked on my phone

I scratched the title box in yellow on a screenshot: make it a fourth choice beside the tabs, showing all three mixed, and fit my name and role on one line each.

Nov 19

Too much red

The first build lit the whole box solid red. Too aggressive at the top, so the box stays white and only the small bar fills red once you scroll.

Nov 19

A name for every part

Black tags on every frame and a key beside each row, so a change reads "H3 bigger on F6". The phone box was then measured: 29 pixels above and below the links.

Nov 19

1.0, live

The landing screen as it went live on dafspace.com: nothing filled until you scroll, three tabs, the list mixing all of them.

What I learned to do

  1. Run a site from plain text drafts and one build script, and preview every version privately before it goes public.
  2. Direct design by marking real screenshots, by frame and by tag, instead of describing changes in the abstract.
  3. Keep the site in its own private repository and connect it to Cloudflare Pages, so every push to main goes live on its own.
  4. Buy a domain and point it at the site: dafspace.com at Porkbun, its DNS on a free Cloudflare zone, the root and www both on HTTPS.
  5. Let search engines in at launch: a sitemap, robots.txt and a canonical address on every page.
  6. Keep one runbook of every account, setting and cost, so the whole setup can be rebuilt, rolled back or moved from it.