On self-updating screenshots

Nick sent me a great post from one of the engineers at Goodenough, the fine folks behind Jelly, on the topic of self-updating screenshots. It is near and dear to my heart: their approach, which uses Puppeteer to programmatically generate screenshots on every deploy, is spiritually adjacent to my own galaxy-brained approach of just using iframes pointed at a live demo site to achieve the same end. Both are gambits to solve the same problem — the pernicious drift between docs and product — and both, in their own way, work. So I figured I'd use this as a launching pad to talk about how our approach has aged, almost a year on. I'll riff across four dimensions: Performance. Puppeteer wins this one, bar none. Once you've captured the images, they are in fact just images — none of the incumbent burden of loading one or multiple iframes and ticking through their lifecycle. We've mitigated this somewhat with lazy loading, but there's no world in which a static asset loses to a live frame on…