What it proves
A small side project gets stronger when the output is portable enough to survive beyond the first demo and useful enough to shape the next conversation.
Planning artifacts
one-page-canvas is the clearest example of a fun project leaving behind a reusable planning artifact.
This is the anchor repo for the planning-artifact track because it does not stop at a pleasant demo. The important part is the plain Markdown page it exports and how easily that page can move into docs, tickets, and review notes.
Why this repo carries the track
A short site-side guide before the proof layer on GitHub.
Why it is the anchor
It teaches the track standard quickly: a narrow tool, a clear one-page structure, and one reusable artifact instead of a larger vague workspace story.
What survives the first run
The exported Markdown canvas is the artifact. It gives the project a handoff shape that can be reused after the browser tab closes.
What the first useful success looks like
one-page-canvas as a first useful success, not only a demo.
The first success is not only that the local canvas opens. It is that the draft becomes one page with enough structure to reuse in a doc, review, or planning thread without rebuilding the thinking from scratch.
Use this when a rough strategy or product-review idea should stay on one page first, then move into a doc, a ticket, or a deck only after the shape is tight enough to travel.
python3 serve_canvas.pyServes the canvas locally at http://127.0.0.1:8765/index.html and lets the draft export into Markdown.Where it routes next
A local-first strategy canvas that keeps one-page planning structured, fast to open, and easy to export into a reusable artifact.