Gokul d2200a4066 docs: refresh demo.gif for the redesigned TUI (#106) ...

* docs: refresh demo.gif for the redesigned TUI

The old demo.gif was recorded against the pre-#104 UI. After the
design-system rebuild (#104) and the extra screens in #105, the
README was showing a GIF that no longer matched the actual tool —
which is worse than having no GIF at all.

Re-record with VHS against the current TUI. The tape drives a tour
of the new Workflows list, Tweaks overlay with accent cycling, DAG
view across three different workflow shapes, Trigger / Secrets /
Help tabs, and a live Podman run so the Execution and Logs tabs
have real streaming output instead of an empty box.

While at it, check in demo.tape so the next person who touches the
UI doesn't have to reverse-engineer a recording session to keep the
GIF in sync. Re-render with \`vhs demo.tape\`.

* docs: scale up demo.gif, show Docker, drop the tape

Three things were off about the first pass.

One: the font was too small. At 14pt on a 1280-wide canvas the TUI
was legible if you squint, but a README GIF needs to be readable at
half-size on someone else's retina display. Bumped to 20pt on a
1680×960 canvas — same layout, just actually readable.

Two: the run was Podman-only, which undersells things. wrkflw
supports Docker, Podman, emulation and secure-emulation, and the
GIF should show that. The tape now cycles all four runtimes with
\`e\` (the runtime badge updates live in the title bar) and then
kicks off the actual run in Docker so the Execution and Logs tabs
stream real container output.

Three: \`demo.tape\` doesn't belong in the repo. It's a build
artifact for the GIF, not source, and keeping it tracked just
invites drift between the tape and whatever is actually rendered.
If someone needs to re-record, \`vhs record\` is a one-liner.

* docs: run both Docker and Podman in the demo

Showing the runtime indicator cycle through four values was
technically correct but a bit hand-wavy — you see the badge change,
not the actual container backend doing work.

Run the same workflow twice: once on Docker, then reset with \`R\`,
cycle the runtime to Podman with \`e\`, and run again. Both
Execution + Logs tabs now show real streaming output with the
runtime badge matching the backend that's actually running, which
is the thing we were trying to demonstrate in the first place.

2026-04-21 23:28:34 +05:30

6.2 MiB

1680x960px

Raw History