Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Update docs screenshots to reflect new navigation design and use the actual in-app example screener

Open
  • Is something wrong?
#528 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
java
Domain
documentation, tooling

Research direction

After #522 and #525 are complete, inspect the screenshot automation scripts in e2e and compare the current docs example with the in-app example screener. Done means the screenshots and any affected docs text reflect the new navigation and actual screener; also document whether combining the scripts or sharing setup is worthwhile.

Written by the indexing model from the issue text.

Description

Depends on #522 and #525 being complete first!

There are a couple of scripts (in e2e I believe) that automate creating screenshots, so maybe that can streamline this task.

Will probably need to update the scripts (and maybe some of the docs text too?) to reflect the content of the in-app example screener instead of the dummy screener that currently is used for docs. (Sanity check that this makes sense before beginning! - is there something gained by keeping the two separate (docs example vs. in-app example).

Bonus: combine the existing screenshot automation scripts into one script (or maybe separate scripts with a common setup? Not sure, but investigate what is best)

Dominant language
Java
Stars
16
Forks
5
Avg merge
14h 45m
Merged PRs (30d)
25

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CodeForPhilly/benefit-decision-toolkit

All issues in CodeForPhilly/benefit-decision-toolkit

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.