The README opening (#49) now spells out capabilities with examples, but a short animated demo would land it harder — show things actually being used in a terminal.
Approach
- Record a short session with
asciinema rec docs/demo.cast against the real Things DB (today → add → edit → complete → search → open).
- Redact personal data by editing the
.cast file directly — it's just JSON frames ([timestamp, "o", "text"]), so real task titles / project names / tags can be swapped for demo strings inline. Keep replacement string lengths close to the originals so cursor positions don't drift.
- Render with
agg docs/demo.cast docs/demo.gif (or keep the cast and embed via asciinema player).
- Wire
docs/demo.gif into the README, just under the lede and above the examples block.
Open questions
- GIF vs. embedded asciinema player vs. SVG (svg-term-cli)?
- Should we commit a
docs/RECORDING.md with the exact commands so re-recording on a CLI surface change is one command?
- Is it worth scripting the redaction (e.g. a small
jq / Go tool that takes a mapping file) so future re-records are mechanical?
The README opening (#49) now spells out capabilities with examples, but a short animated demo would land it harder — show
thingsactually being used in a terminal.Approach
asciinema rec docs/demo.castagainst the real Things DB (today→add→edit→complete→search→open)..castfile directly — it's just JSON frames ([timestamp, "o", "text"]), so real task titles / project names / tags can be swapped for demo strings inline. Keep replacement string lengths close to the originals so cursor positions don't drift.agg docs/demo.cast docs/demo.gif(or keep the cast and embed via asciinema player).docs/demo.gifinto the README, just under the lede and above the examples block.Open questions
docs/RECORDING.mdwith the exact commands so re-recording on a CLI surface change is one command?jq/ Go tool that takes a mapping file) so future re-records are mechanical?