"Git hook[ed]” on images & up your documentation game
summary
Argues that committing images with code makes visual history searchable and speeds onboarding, shows a working workflow that auto-takes screenshots on commit using git hooks and puppeteer/pyppeteer, and wires images into version control for click-to-view diffs. Notes industry tooling like screenshot diffing and design systems (Sketch/Abstract), reports a nearly 50/50 love/hate split and cites ~65% visual learners, and demonstrates a prototype that mostly works and cuts time spent manually hunting old visual states.
AI-written summary · about
chapters (5)
- 0:00Start
- 8:31What commit message should we make?
- 10:46What does a design process look like?
- 21:12A "Git" for design!
- 26:52Make your own!
related talks
04mVisual Version History
05mBetter Living through Git Hooks
43mPut Git to work: increase the quality of your project
38mCommunicating Intent Through Git
01h 29mBetter Code and Collaboration through Open Source Concepts, Dev Containers....
29mDocumentation Tradeoffs and Why Good Commits Matter
05mGit as a continuous manager
09mTelling stories through your commits