README screenshots and two How to Play lines describe the old interface
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- css, html, javascript
- Domain
- documentation, frontend
Research direction
Start with README.md lines 121-125, 161 and 169, and check the claims against the live game and index.html:30-51, which holds the captured-piece bars. The promotion chooser is described at line 72 of the same file. Done means both screenshots in assets/screenshots/ show the current layout with the caption updated, lines 161 and 169 match the behaviour, and npm run format passes.
Written by the indexing model from the issue text.
Description
Summary
The README's two screenshots and two "How to Play" lines describe the game as it was before the recent features and layout changes, so the README no longer matches the live site.
Where
README.md:121-125(screenshots and caption)README.md:161(promotion)README.md:169(captured pieces)assets/screenshots/ui-with-settings.png,assets/screenshots/ui-without-settings.png
Details
- Screenshots. Both images were last changed on 2025-11-02. Since then
index.htmland the stylesheets have had 22 commits, including the Hint, Offer draw and Resign buttons, the clock, the captured-piece bars beside the board, the Load PGN and Copy FEN buttons and the folded "Settings" section (seeCHANGELOG.md, Unreleased). The caption "without settings panel (left) and with settings panel (right)" refers to a layout that no longer exists. - Line 161 says "A pawn that reaches the last rank becomes a queen". The game shows a chooser for queen, rook, bishop or knight, as line 72 of the same file says.
- Line 169 says the captured pieces "are shown under the Move History". They are now in a bar for each player beside the board (
index.html:30-51).
Impact
Visitors deciding whether to try the game see an interface it no longer has, and two instructions that are wrong.
Suggested fix
- Retake both screenshots from the live site, for example one of a game in progress and one with "Settings" open, and update the caption.
- Line 161: "A pawn that reaches the last rank is promoted; choose a queen, rook, bishop or knight".
- Line 169: say the captured pieces and the material lead are shown in each player's bar beside the board.
Acceptance criteria
- Both screenshots show the current layout
- Lines 161 and 169 match the game's behaviour
Related: #48
Getting started
- Relevant files:
README.md,assets/screenshots/ - How to run tests:
npm run format(Prettier checks Markdown)
Filed by repo-audit/pages-audit at 0144de7. Severity: low. Effort: S. audit-key: documentation|README.md|screenshots
- Dominant language
- JavaScript
- Stars
- 4
- Forks
- 2
- Avg merge
- 4h 8m
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from TMHSDigital/Static_Chess
-
enhancement good first issue severity: low
Difficulty 1/5 Under an hour Newbie friendliness 88/100
TMHSDigital/Static_Chess#77 ·
-
enhancement good first issue severity: low
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
TMHSDigital/Static_Chess#76 ·
-
enhancement good first issue severity: low
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
TMHSDigital/Static_Chess#75 ·
-
enhancement good first issue severity: low
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
TMHSDigital/Static_Chess#72 ·
-
documentation good first issue severity: low
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
TMHSDigital/Static_Chess#49 ·
All issues in TMHSDigital/Static_Chess
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
discovery:other factory-active task-identify-harness-labels-done task-identify-issue-type-done
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
vercel/ai#25068 · 4 comments ·
Maintainers usually reply within 1 day
-
needs-triage typo
Difficulty 1/5 Under an hour Newbie friendliness 88/100
llm-d-incubation/llm-d-scaling-manager#122 ·
Maintainers usually reply within 1 day
-
create-strapi-app doesn't await writing license.txt, so a failed write skips its error handlingOpenflag: invalid template issue: bug severity: low source: cli status: pending reproduction version: 5
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
strapi/strapi#28637 · 1 comment ·
Maintainers usually reply within 2 days