feat: splashes of colour on the working pages #56

New issue

deadstyle · 2026-10-08T13:45:32-05:00

deadstyle commented

2026-10-08 13:45:32 -05:00

Problem

Add splashes of colour here and there on the working pages.

(PM's words. No investigation or plan yet.)

🤖 Carried over from GitHub issue GH-6.

## Problem Add splashes of colour here and there on the working pages. (PM's words. No investigation or plan yet.) --- 🤖 Carried over from GitHub issue GH-6.

deadstyle commented

2026-10-08 13:45:40 -05:00

🤖 Product question: which pages, and how much colour? The ticket doesn't say, and docs/design.md has no colour guidance, so I haven't started.

Today colour appears in borders, the breadcrumb and mode badge, CI pass/fail/running marks, and the splash. The list rows and Details text are mostly plain grey/white.

Light touch. Colour only meaning that already exists: change-request state (open green, draft dim, merged mauve, closed red), the ★ Renovate marker and update-type tags (major red, minor yellow, patch green), and labels. Nothing decorative. Cost: small, about half a day.
Accents everywhere. Option 1, plus coloured box titles per box, author names, branch names, counts and the keys in hints. The screens get livelier but busier. Cost: about a day, and more screenshots to judge.
You pick the pages. Tell me which pages feel flat and I'll colour those.

Recommendation: option 1. Colour that carries meaning is easier to skim and doesn't clash with the existing palette.

🤖 **Product question: which pages, and how much colour?** The ticket doesn't say, and `docs/design.md` has no colour guidance, so I haven't started. Today colour appears in borders, the breadcrumb and mode badge, CI pass/fail/running marks, and the splash. The list rows and Details text are mostly plain grey/white. 1. **Light touch.** Colour only meaning that already exists: change-request state (open green, draft dim, merged mauve, closed red), the ★ Renovate marker and update-type tags (major red, minor yellow, patch green), and labels. Nothing decorative. Cost: small, about half a day. 2. **Accents everywhere.** Option 1, plus coloured box titles per box, author names, branch names, counts and the keys in hints. The screens get livelier but busier. Cost: about a day, and more screenshots to judge. 3. **You pick the pages.** Tell me which pages feel flat and I'll colour those. **Recommendation:** option 1. Colour that carries meaning is easier to skim and doesn't clash with the existing palette.

deadstyle added the

feature

needs-pm

labels

2026-10-08 13:46:06 -05:00

deadstyle referenced this issue from a commit

2026-10-08 13:46:16 -05:00

chore: track tickets on Forgejo instead of GitHub

deadstyle referenced this issue

2026-10-08 13:46:34 -05:00

chore: track tickets on Forgejo instead of GitHub #57

deadstyle commented

2026-10-08 14:24:42 -05:00

🤖 PM answered: do ideas 1–3 (colour repo rows by what needs attention, split issue/PR rows into roles, per-box title accents), Repos screen first, then judge from screenshots. Mode: inline (single domain, internal/ui).

deadstyle referenced this issue from a commit

2026-10-08 14:25:38 -05:00

feat(ui): colour the working pages by meaning

deadstyle referenced this issue

2026-10-08 14:25:40 -05:00

feat(ui): colour the working pages by meaning #58

deadstyle referenced this issue from a commit

2026-10-08 14:34:27 -05:00

feat(ui): per-box border and row accents

deadstyle referenced this issue from a commit

2026-10-08 14:36:48 -05:00

feat(ui): colour the Renovate view's boxes and update types