Problem
The Kanban WebUI currently displays too much interface text in forced uppercase / ALL CAPS.
This makes the board harder to read during normal use, especially when there are many task cards, assignees, statuses, and metadata fields on screen. It also makes the interface feel visually noisy, as if every card is shouting.
This is not only a cosmetic preference. In a developer/workflow tool, exact text matters. Profile IDs, task titles, task IDs, commands, paths, and user-entered content should be displayed in the same case that users typed or that the backend stores.
Related history:
Expected behavior
The Kanban WebUI should use normal-case text by default.
Examples:
worker, not WORKERphantom, not PHANTOM- task titles shown as written
- task descriptions shown as written
- assignee/profile names shown exactly as canonical stored IDs
- input/dropdown values shown exactly as submitted/stored
Uppercase styling should only be used for very small decorative static labels where it does not affect readability or exact-value interpretation.
Actual behavior
Many Kanban UI elements are visually forced into uppercase. This makes the board harder to scan and can obscure whether values are actually uppercase or only styled that way.
Suggested fix
Audit the Kanban frontend for uppercase transforms, including:
- CSS:
text-transform: uppercase
- Tailwind:
uppercase
- JavaScript/TypeScript:
.toUpperCase()
Remove forced uppercase from user-facing content fields, including:
- task titles
- task descriptions
- assignee/profile names
- task IDs
- status labels
- input fields
- dropdown values
- card metadata
- buttons/headers where readability is affected
If uppercase is kept anywhere, it should be limited to small static labels only.
Why this matters
Kanban is a working interface that users may keep open all day. Readability matters. Forced ALL-CAPS reduces scanability, increases cognitive load, and makes exact case-sensitive values harder to understand.
Environment
Hermes Kanban WebUI / dashboard.
Problem
The Kanban WebUI currently displays too much interface text in forced uppercase / ALL CAPS.
This makes the board harder to read during normal use, especially when there are many task cards, assignees, statuses, and metadata fields on screen. It also makes the interface feel visually noisy, as if every card is shouting.
This is not only a cosmetic preference. In a developer/workflow tool, exact text matters. Profile IDs, task titles, task IDs, commands, paths, and user-entered content should be displayed in the same case that users typed or that the backend stores.
Related history:
Expected behavior
The Kanban WebUI should use normal-case text by default.
Examples:
worker, notWORKERphantom, notPHANTOMUppercase styling should only be used for very small decorative static labels where it does not affect readability or exact-value interpretation.
Actual behavior
Many Kanban UI elements are visually forced into uppercase. This makes the board harder to scan and can obscure whether values are actually uppercase or only styled that way.
Suggested fix
Audit the Kanban frontend for uppercase transforms, including:
text-transform: uppercaseuppercase.toUpperCase()Remove forced uppercase from user-facing content fields, including:
If uppercase is kept anywhere, it should be limited to small static labels only.
Why this matters
Kanban is a working interface that users may keep open all day. Readability matters. Forced ALL-CAPS reduces scanability, increases cognitive load, and makes exact case-sensitive values harder to understand.
Environment
Hermes Kanban WebUI / dashboard.