JarbasHiveMind / JarbasHiveMind/hivemind-admin-panel
Admin panel + CLI UX backlog (12-reviewer audit, validated against dev)
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 30
Description
> 🤖 Auto-generated by Claude Opus 5 (claude-opus-5) via Claude Code — NOT human-reviewed. Verify before acting.
This is a twelve-reviewer UX audit of the admin panel and CLI — two UX leads plus ten user personas. The audit itself ran against a checkout 43 commits behind dev, so roughly half the original findings were already fixed by the time I looked at them. Every item below has been re-checked against current origin/dev and is grouped by where it stands. The full ranked write-up is available as the audit artifact if you want the details.
This is a living checklist. I'll strike items as they land rather than leaving comments.
Fixed this pass, in draft PRs held for live validation on ser9:
- [ ] Add Client discarded the credentials it just created → #42. Real on current dev; the reveal UI with copy buttons is in that PR.
- [ ] The panel died silently on a bind failure, daemon thread exiting while the process stayed reported as healthy → #43. Real on current dev; fixed with bounded retry and startup-error reporting.
Validated, still open:
- [ ] **No focus ring on a keyboard-only tab.** `focus-visible` appears nowhere in the panel: zero occurrences in `static/css/style.css`, `static/index.html` and `static/js/app.js`. Only four places style `:focus` at all — form inputs, textareas and selects at `static/css/style.css:275-277`, the topology nodes at `:283`, and the config editor at `:718`. Every button, link and navigation item shows the browser default or nothing, so a keyboard user cannot see where they are.
- [ ] **The hive map is an unlabelled graphic.** The topology `
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by selecting one validated finding and inspect the cited entries in static/css/style.css, static/index.html, or static/js/app.js against current dev. Reproduce the accessibility behavior in the panel, then confirm the chosen issue is addressed without reopening the already-fixed findings; no test file is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, html, javascript, python
- Domain
- accessibility, backend, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100