[Docs] - Update Actual Screenshots #1621

New Issue

GiteaMirror · 2026-02-28T19:48:59-06:00

GiteaMirror commented

2026-02-28 19:48:59 -06:00

Originally created by @joel-jeremy on GitHub (Nov 26, 2024).

Description

Some of the screenshots throughout the docs are outdated. It would be great if these updated to newer screenshots.

Documentation URL

https://deploy-preview-504.www.actualbudget.org/docs/

Originally created by @joel-jeremy on GitHub (Nov 26, 2024). ### Description Some of the screenshots throughout the docs are outdated. It would be great if these updated to newer screenshots. ### Documentation URL https://deploy-preview-504.www.actualbudget.org/docs/

GiteaMirror added the documentation label 2026-02-28 19:48:59 -06:00

GiteaMirror commented

2026-02-28 19:49:00 -06:00

@RubenOlsen commented on GitHub (Jan 3, 2025):

Unless you can point to particular screenshots, these will mostly be updated when someone updates the documents.

@RubenOlsen commented on GitHub (Jan 3, 2025): Unless you can point to particular screenshots, these will mostly be updated when someone updates the documents.

GiteaMirror commented

2026-02-28 19:49:00 -06:00

@omachala commented on GitHub (Feb 3, 2026):

Hi! I'd be happy to help audit the docs and update the outdated screenshots.

I maintain a tool called heroshot that automates screenshot capture - you define what pages/states to capture in a config file and it handles the rest using Playwright. This makes ongoing maintenance much easier since anyone can regenerate screenshots when the UI changes.

I'll take a look at the docs, identify which screenshots need updating, and can submit a PR with the updates. Would you also like me to include a heroshot config so future updates are easier for maintainers?

@omachala commented on GitHub (Feb 3, 2026): Hi! I'd be happy to help audit the docs and update the outdated screenshots. I maintain a tool called [heroshot](https://heroshot.sh) that automates screenshot capture - you define what pages/states to capture in a config file and it handles the rest using Playwright. This makes ongoing maintenance much easier since anyone can regenerate screenshots when the UI changes. I'll take a look at the docs, identify which screenshots need updating, and can submit a PR with the updates. Would you also like me to include a heroshot config so future updates are easier for maintainers?

GiteaMirror commented

2026-02-28 19:49:01 -06:00

@youngcw commented on GitHub (Feb 3, 2026):

I would be interested in an automated screenshot system. Now that the docs package is integrated into the main repo we can pull directly from the VRT screenshots, or generating them on the fly could work too. Can your tool add to screenshots? Like adding arrows or boxes to highlight specific areas?

@youngcw commented on GitHub (Feb 3, 2026): I would be interested in an automated screenshot system. Now that the docs package is integrated into the main repo we can pull directly from the VRT screenshots, or generating them on the fly could work too. Can your tool add to screenshots? Like adding arrows or boxes to highlight specific areas?

GiteaMirror commented

2026-02-28 19:49:01 -06:00

@omachala commented on GitHub (Feb 3, 2026):

Great question! Heroshot focuses on capturing clean, accurate screenshots but doesn't have built-in annotation features (arrows, boxes, etc.).

For annotations, you could:

Use heroshot to capture the base screenshots automatically
Add annotations in a second pass using tools like Excalidraw, Figma, or even ImageMagick scripts

That said, heroshot could still help a lot with the 'keep screenshots in sync with UI changes' problem - you'd regenerate the base screenshots whenever the UI updates, then just re-apply annotations to the few that need them.

Would you like me to audit the docs and identify which screenshots need updating? Happy to help get things started!

@omachala commented on GitHub (Feb 3, 2026): Great question! Heroshot focuses on capturing clean, accurate screenshots but doesn't have built-in annotation features (arrows, boxes, etc.). For annotations, you could: 1. Use heroshot to capture the base screenshots automatically 2. Add annotations in a second pass using tools like Excalidraw, Figma, or even ImageMagick scripts That said, heroshot could still help a lot with the 'keep screenshots in sync with UI changes' problem - you'd regenerate the base screenshots whenever the UI updates, then just re-apply annotations to the few that need them. Would you like me to audit the docs and identify which screenshots need updating? Happy to help get things started!