FIRST-Tech-Challenge / FIRST-Tech-Challenge/scorekeeper
Scoring icon and layout consistency across different pages
- Dominant language
- No language data
- Stars
- 110
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
**Is your feature request related to a problem? Please describe.**
I am a volunteer that often performs or assists with a variety of roles throughout an event. I will be assigned penalty referee or head referee, but over the course of an event I will:
- train score trackers
- help setup the score system
- help train new scorekeepers
- review scores on a score tracking tablet
- Review scores on the head ref tablet
- Help edit and/or review edits made by the scorekeeper
Which means I will be frequently viewing or interacting with the following pages:
- Score tracking (auto/teleop/review pages)
- Main head ref page with score detail drop-downs
- Score sheet tab on the head ref page
- Score edit page on the match control page
All these pages use completely different layouts, colors, and icons to represent scoring. It is frustrating when I switch between views and have to completely reorient my thinking around a different layout and spend time searching the page for what I’m looking for.
The scoresheet page under Match Results also uses the same formatting as the score sheet view on the head ref tablet and should also be included in any redesigns to make formatting consistent.
**Describe the solution you'd like**
I would like to see the score system for the 2024-2025 season and beyond use consistent formatting across most or all of the pages I listed above. I realize that the different use of the pages will require at least some changes, but design consistency across them would facilitate quicker communication between head referees, score trackers, and score keepers.
**Describe alternatives you've considered**
n/a
**Additional context**
Score tracker screen example:

Match control page:

Head ref scoresheet page:

Head ref active match page:

Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.