github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 15:12:35 -05:00
Code Issues 1.5k Packages Projects Releases 54 Wiki Activity

[GH-ISSUE #6188] [Docs] - Update Actual Screenshots #43280

New Issue
Open
opened 2026-04-26 03:35:36 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-04-26 03:35:36 -05:00
Owner
Copy Link

Originally created by @joel-jeremy on GitHub (Nov 26, 2024).
Original GitHub issue: https://github.com/actualbudget/actual/issues/6188

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). Original GitHub issue: https://github.com/actualbudget/actual/issues/6188 ### 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-04-26 03:35:36 -05:00
GiteaMirror commented 2026-04-26 03:35:38 -05:00
Author
Owner
Copy Link

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

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

<!-- gh-comment-id:3544400031 --> @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-04-26 03:35:38 -05:00
Author
Owner
Copy Link

@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?

<!-- gh-comment-id:3843183571 --> @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-04-26 03:35:39 -05:00
Author
Owner
Copy Link

@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?

<!-- gh-comment-id:3843202937 --> @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-04-26 03:35:39 -05:00
Author
Owner
Copy Link

@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!

<!-- gh-comment-id:3843447876 --> @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!
GiteaMirror commented 2026-04-26 03:35:40 -05:00
Author
Owner
Copy Link

@Juulz commented on GitHub (Apr 8, 2026):

Note to screenshot updaters...

Almost all of the screenshots in the credit card docs section were built specifically with the test demo set up in sync with the text and will need to be hand redone if/when it's decided they are out of date.

A few others I have worked on this last week (tour) also are set up specifically with the accompanying text. Those will need to be identified so the text and screenshot match. I know there have been others.

<!-- gh-comment-id:4205849061 --> @Juulz commented on GitHub (Apr 8, 2026): Note to screenshot updaters... Almost all of the screenshots in the credit card docs section were built specifically with the test demo set up in sync with the text and will need to be hand redone if/when it's decided they are out of date. A few others I have worked on this last week (tour) also are set up specifically with the accompanying text. Those will need to be identified so the text and screenshot match. I know there have been others.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label documentation
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#43280
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?