field notes
Blog
Notes on screenshot automation, visual debt, and keeping docs current.
How to Keep Documentation Screenshots Always Up to Date
Five methods to keep documentation screenshots current — from manual audits to fully automated CI/CD capture — with working code, a cost comparison, and a decision framework.
How to Capture Documentation Screenshots Behind Login
Authentication is the #1 blocker for automated documentation screenshots. Four approaches solve it — localhost capture, session persistence, cookie injection, and short-lived token URLs. Here is when to use each.
The Real Cost of Outdated Documentation Screenshots
A B2B SaaS product with 100 screenshots spends $6,000–$12,000 per year on manual maintenance — before counting support tickets. Here is the full cost model, with a formula you can apply to your own docs.
Screenshots as Code for Docs
Screenshots-as-code treats documentation visuals as automated artifacts: defined in config, reviewed in diffs, and refreshed with the product.
What Is Visual Debt (and Why Your Docs Are Lying to Users)
Visual debt is the accumulated gap between your product's current interface and the screenshots in your docs. It compounds every release, and most teams have no mechanism to pay it down.
Run one real docs capture in CI. Keep the same URL current after every ship.
Start for free or jump into the docs.