Make practice games useful for campus placement preparation
Maintainer antworten meist innerhalb von 1 Tag
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Anfängerfreundlichkeit
- 25/100
Rechercherichtung
Start with related planning issue #22 and the games hub and landing page; the payload does not name their file paths. Define the intended skills and student journeys, then review how the existing Pattern Sprint and Digit Recall pages present rules, feedback, difficulty, accessibility, and practice guidance. Done means the hub explains playable games accurately, each exercise has clear learning feedback and guidance, and student feedback is gathered before expanding the catalog.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Context
The current games are Pattern Sprint and Digit Recall. They are original short exercises, but the games page describes them as a quick break and does not explain how they help with campus-placement preparation.
Proposal
Make the games area a useful placement-practice space. First define the skills and student journeys it should support; then improve the exercises, feedback, and page copy to match. Begin with areas that fit short browser rounds, such as quantitative aptitude and logical reasoning, and evaluate coding or interview practice with students before expanding.
Acceptance criteria
- Describe the intended placement-preparation skills for each exercise and avoid implying that the games predict or guarantee hiring outcomes.
- Provide a clear explanation after each answer and useful difficulty progression or practice guidance.
- Review questions and answers for correctness, clarity, and original authorship.
- Keep the core practice flow free, mobile-friendly, keyboard-accessible, and usable without login.
- State clearly that the content is independent practice, not an official assessment from an employer.
- Gather student feedback before expanding the game catalog.
Related planning issue: #22.
Implementation plan
Build original placement-practice games in focused contributions. All core practice remains free and available without login. Start small, gather student feedback, then expand the catalogue.
Foundation and first release
- #58 Shared catalogue, rules boundaries and session lifecycle
- #59 Switch Challenge: symbols and shapes
- #60 Digit Challenge: constrained arithmetic
- #61 Grid Challenge: spatial memory and symmetry
- #69 Browser history and per-game progress; can begin after the first game
Additional skill practice
- #62 Motion Challenge: standard and axis-restricted boards
- #63 Deductive Challenge: missing-symbol grids
- #64 Inductive Challenge: visual odd-one-out
- #65 Bubble Math: order expression values
- #68 Colour-position recall
Planning games and mixed sessions
- #66 Path Finder: rotatable arrow blocks
- #67 Key and Door: directed maze planning
- #70 Mixed timed practice; begins after at least three stable game families
This issue also owns the games hub and landing-page framing: show the skill, mode, difficulty and expected duration; link to instructions and relevant practice. Keep existing game links working. Do not advertise games or modes before they are playable.
Each game issue requires original puzzles/assets, explained rules/scoring, useful learning feedback, keyboard/touch controls and meaningful generator/evaluation tests. Quick-calculation and multiple-gap variants can follow the arithmetic/deductive foundations; no separate backend, public leaderboard or paid access is needed for this release.
- Vorherrschende Sprache
- TypeScript
- Sterne
- 1
- Forks
- 1
- Ø Merge
- 8 Std. 58 Min.
- Gemergte PRs (30 T.)
- 37
Entwicklungsumgebung
- Enthält ein Dockerfile oder eine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus procoderji-com/procoderji
-
area:frontend bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 62/100
procoderji-com/procoderji#104 ·
Maintainer antworten meist innerhalb von 1 Tag
-
enhancement good first issue
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 88/100
procoderji-com/procoderji#36 ·
Maintainer antworten meist innerhalb von 1 Tag
-
enhancement good first issue
Schwierigkeit 1/5 1-3 Stunden Anfängerfreundlichkeit 85/100
procoderji-com/procoderji#35 ·
Maintainer antworten meist innerhalb von 1 Tag
-
enhancement good first issue
Schwierigkeit 1/5 1-3 Stunden Anfängerfreundlichkeit 79/100
procoderji-com/procoderji#34 ·
Maintainer antworten meist innerhalb von 1 Tag
-
enhancement good first issue
Schwierigkeit 1/5 1-3 Stunden Anfängerfreundlichkeit 90/100
procoderji-com/procoderji#33 ·
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in procoderji-com/procoderji
Ähnliche Issues
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
Maintainer antworten meist innerhalb von 1 Tag
-
bug platform-android
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
Termix-SSH/Mobile#146 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 2 Tagen
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 66/100
devswha/herdr-web-ui#3875 ·
-
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 88/100
-
area: runtime chore cli consistency dependencies developer-experience difficulty: easy discovery documentation enhancement good first issue help wanted hygiene json-output packaging priority: P3 tests version
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
Maintainer antworten meist innerhalb von 1 Tag