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

The README image description still names Home's retired panels

Open Beginner friendly
#1,470 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Domain
documentation, testing-qa

Research direction

Start at README.md:85 and run make demo-home to compare the image alt text with the visible Home panel headings. Update the description to match the current layout, add the requested documentation check for retired names, and verify the rendered README and demo acceptance criteria. Record the corrected description in invalidates.

Written by the indexing model from the issue text.

Description

area:chat bug good first issue sev:papercut

Seen on dev@debffabf6. Surfaced while verifying #1415; not introduced by it.

What happened

The Home screenshot's alt text says scheduled and names the older panel arrangement. The current Home panel is standing; the text gives screen-reader users a description of a different page.

Replication

Deterministic (no model). Read the Home image alt text in README.md, then run make demo-home and inspect Home's panel headings. The alt text includes scheduled; the live heading is standing.

Where

README.md:85 at dev@debffabf6 contains Home in two columns: needs you, unread, where you were, running and scheduled on the left; projects, spend and since you left on the right.

The fix

Describe the screenshot and current Home layout in the image's alt text using the visible panel names.

Acceptance

  • e2e: the rendered README's Home image has alt text matching the headings in codeaf chat on a demo home.
  • Unit: a documentation check catches retired Home panel names in current image descriptions.
  • Record the corrected description in invalidates.
Dominant language
Go
Stars
115
Forks
14
Avg merge
9h 38m
Merged PRs (30d)
730

Contributor guide

No contributing guide indexed for this repository

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 Agent-Field/CodeAF

All issues in Agent-Field/CodeAF

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.