UI design polish: badge placement and plain-language copy
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
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start with the settings page components and their copy; the issue does not name specific files, so locate them from the UI entry point. Review the checkbox badge in light and dark themes and identify settings whose labels use technical language. Done means the badge is clearly associated with its field, each technical setting has a plain-language hint, all UI strings remain English, and before/after screenshots are attached to the pull request.
Written by the indexing model from the issue text.
Description
Problem
Screenshots of the settings pages show some rough edges for people who are not developers:
- The "Built-in value" badge on checkboxes looks detached from the field it belongs to.
- Copy is technical, for example "Token budget", "as OpenRouter spells it", and the model id in monospace without explanation.
Acceptance criteria
- Place the badge so it clearly belongs to its field (next to the label or value), in light and dark theme.
- Add a short plain-language hint to each setting that currently only has a technical name, and describe what the setting changes in practice.
- Keep all UI strings in English.
- Attach before/after screenshots to the pull request.
This is a good candidate for a first contribution.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 1
- Avg merge
- 1h 20m
- Merged PRs (30d)
- 309
Getting set up
- Ships a 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 ExpidetGames/code-reviewer
-
area: app type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ExpidetGames/code-reviewer#585 ·
Maintainers usually reply within 1 day
-
area: app type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
ExpidetGames/code-reviewer#584 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ExpidetGames/code-reviewer#464 ·
Maintainers usually reply within 1 day
-
area: app type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
ExpidetGames/code-reviewer#308 ·
Maintainers usually reply within 1 day
-
type: docs
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ExpidetGames/code-reviewer#94 ·
Maintainers usually reply within 1 day
All issues in ExpidetGames/code-reviewer
Similar issues
-
agent/scanner help wanted hive/claimed-by-scanner kind/bug stage/020-claimed
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
hivecommons/rationguard#315 ·
Maintainers usually reply within 1 day
-
agent-ready area: ui-sdk priority: p3 type: chore
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
schlessera/brain-kit#2534 ·
Maintainers usually reply within 1 day
-
bug lane:gh-5
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
LLM-4-People/bridlewise-testing#122 ·
Maintainers usually reply within 1 day
-
bug priority: P2
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
enhancement priority:low ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day