GitHub Pages Deploy
Developers wanted to look at the wireframes on their own time without running bob-wire on their own machine.
One command now publishes every wireframe to a web address. It was meant as a stopgap until bob-wire could move to Cloudflare like the design site.
What changed
The change that matters most, in plain words. Open any one to see it.
- 1
Anyone with access can browse every wireframe at one address, without installing anything.
Wireframes on the web · came from Mark Parson
- GitHub Pages was chosen for now; Cloudflare Pages, which deploys on every push, is the long-term home. In words
How we got here
Each change, traced back to the conversation it came from. A solid mark means the record names the source; a dashed one was matched by the draft and waits for review.
From the record: no recorded conversation behind this one.
bob-wire-c7-D1 Publish to GitHub Pages as a temporary home; migrate to Cloudflare Pages once the Wire* components no longer block it. — Mark Parson
bob-wire-c7-D2 Inject the base URL at deploy time, not in the config, so local dev keeps working at the root; push dotfiles so GitHub Pages skips Jekyll and keeps the asset folder. — Mark Parson
Anyone with access can browse every wireframe at one address, without installing anything.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Put the wireframes online
The record names no one; every commit in this cycle is authored by Mark Parson (git), so the credit is matched from authorship.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 0
The full record 3 decisions · 0 key-change entries · 290 words · 0 captures
The record stays as written, for agents and for audit: Key Changes, every decision, the artifacts and the visual record.
Open the record for c7 →