fix(feedback): improve contrast of hero text (BUNYIP-45) #49

Merged
David merged 1 commit from fix/feedback-hero-bunyip-contrast into main 2026-06-03 15:18:01 +02:00
Owner

BUNYIP-45: Improve the contrast for some text

Problem

On the feedback page (/feedback), the word "Bunyip" in the hero heading "Tell us what would make Bunyip better." was hard to read in every theme. It used a static gradient (text-gradient bg-gradient-to-r from-primary via-indigo-500 to-teal-400), which resolves to dark-green (#2f4e2e) at the start fading to light blue-green (#84afb6) at the end. Because those stops are theme-independent, one end always blends into the background: the dark-green start vanishes on the dark theme, and the light blue-green end vanishes on the light and high-contrast themes. The reporter attached dark, light, and high-contrast screenshots all showing the same low-contrast wordmark.

Fix

Replace the gradient on that one span with the solid, theme-aware brand color the landing hero already uses: text-bunyip-reed-900 dark:text-bunyip-reed-50. This keeps the brand emphasis on the wordmark while staying legible across dark, light, and high-contrast modes (reed-900 dark-green on the light/high-contrast white background, reed-50 near-white on the dark/dark-high-contrast background). Both utilities are already present in the compiled bunyip-web/assets/styles.css, so no asset rebuild was needed.

Scope

One-line change in bunyip-web/src/handlers/content.rs (feedback_form). No CSS, behavior, or layout changes.

🤖 Generated with Claude Code

## BUNYIP-45: Improve the contrast for some text ### Problem On the feedback page (`/feedback`), the word "Bunyip" in the hero heading "Tell us what would make Bunyip better." was hard to read in every theme. It used a static gradient (`text-gradient bg-gradient-to-r from-primary via-indigo-500 to-teal-400`), which resolves to dark-green (`#2f4e2e`) at the start fading to light blue-green (`#84afb6`) at the end. Because those stops are theme-independent, one end always blends into the background: the dark-green start vanishes on the dark theme, and the light blue-green end vanishes on the light and high-contrast themes. The reporter attached dark, light, and high-contrast screenshots all showing the same low-contrast wordmark. ### Fix Replace the gradient on that one span with the solid, theme-aware brand color the landing hero already uses: `text-bunyip-reed-900 dark:text-bunyip-reed-50`. This keeps the brand emphasis on the wordmark while staying legible across dark, light, and high-contrast modes (reed-900 dark-green on the light/high-contrast white background, reed-50 near-white on the dark/dark-high-contrast background). Both utilities are already present in the compiled `bunyip-web/assets/styles.css`, so no asset rebuild was needed. ### Scope One-line change in `bunyip-web/src/handlers/content.rs` (`feedback_form`). No CSS, behavior, or layout changes. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
fix(feedback): raise contrast of hero "Bunyip" wordmark
All checks were successful
Check / fmt / clippy / build / test (pull_request) Successful in 4m24s
Create release / Create release from merged PR (pull_request) Has been skipped
d85b113a87
The feedback hero rendered "Bunyip" with a static gradient (from-primary #2f4e2e dark-green via reed-500 to teal-400 #84afb6 light blue-green). Because the gradient stops are theme-independent, one end always blends into the background: the dark-green start disappears on the dark theme while the light blue-green end disappears on the light and high-contrast themes.

Swap the gradient for the solid, theme-aware brand color the landing hero already uses (text-bunyip-reed-900 dark:text-bunyip-reed-50), which keeps the brand emphasis while staying legible in dark, light, and high-contrast modes. Both utilities are already in the compiled stylesheet, so no asset rebuild is required.

#BUNYIP-45
David merged commit dbe79c9aad into main 2026-06-03 15:18:01 +02:00
David deleted branch fix/feedback-hero-bunyip-contrast 2026-06-03 15:18:01 +02:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
psa-systems/bunyip!49
No description provided.