yolo/arr
3
0
Fork 0
Code Issues 12 Pull Requests Actions Packages Projects Releases Wiki Activity

Drop the header verdict and centre the rail #166

New Issue
Closed
opened 2026-08-24 11:23:47 +01:00 by naps62-yolo · 0 comments
naps62-yolo commented 2026-08-24 11:23:47 +01:00
Owner
Copy Link
Copy Source

Two problems with the top rail.

"all signals nominal" occupies the middle of the header permanently to say that
nothing happened. The lamp beside the wordmark already carries that.

.rail is full-bleed — padding: var(--space-3) var(--space-6) with no inner
wrapper — while .deck is max-width: 68rem. On a wide screen the header
spans edge to edge and the content sits centred in a narrower column, so the
wordmark, the search box and the version readout line up with nothing.

What to change

Remove #master-verdict entirely: the element, its styling, and the code in
web/src/main.ts that writes into it, in every state including degraded and
unreachable. The lamp becomes the only header signal, and
masterLamp.dataset.state already distinguishes ok, degraded,
unreachable and probing.

Fault detail is not lost — the health board (.board) already reports every
check with its detail string. Confirm the degraded and daemon-unreachable cases
still surface there before deleting the header copy, and if a detail only ever
appeared in the header, move it to the board.

Wrap the rail's contents in a container capped at the same 68rem and centred,
so the header aligns with the deck below it. The rail's own background, border
and shadow stay full-bleed; only its contents are constrained.

Done looks like

  • No verdict text in the header in any state.
  • A degraded or unreachable daemon is still visible: the lamp changes and the
    health board names the failing check.
  • On a wide viewport the wordmark aligns with the left edge of the deck content
    and the version readout with its right edge.
  • Verified in the browser at a wide viewport and at both mobile breakpoints.

Non-goals

  • The lamp, the nav buttons, the search box and the version readout all stay.
  • The health board's own layout is not part of this change.

Depends on: #159

Two problems with the top rail. "all signals nominal" occupies the middle of the header permanently to say that nothing happened. The lamp beside the wordmark already carries that. `.rail` is full-bleed — `padding: var(--space-3) var(--space-6)` with no inner wrapper — while `.deck` is `max-width: 68rem`. On a wide screen the header spans edge to edge and the content sits centred in a narrower column, so the wordmark, the search box and the version readout line up with nothing. ## What to change Remove `#master-verdict` entirely: the element, its styling, and the code in `web/src/main.ts` that writes into it, in every state including `degraded` and `unreachable`. The lamp becomes the only header signal, and `masterLamp.dataset.state` already distinguishes `ok`, `degraded`, `unreachable` and `probing`. Fault detail is not lost — the health board (`.board`) already reports every check with its detail string. Confirm the degraded and daemon-unreachable cases still surface there before deleting the header copy, and if a detail only ever appeared in the header, move it to the board. Wrap the rail's contents in a container capped at the same `68rem` and centred, so the header aligns with the deck below it. The rail's own background, border and shadow stay full-bleed; only its contents are constrained. ## Done looks like - No verdict text in the header in any state. - A degraded or unreachable daemon is still visible: the lamp changes and the health board names the failing check. - On a wide viewport the wordmark aligns with the left edge of the deck content and the version readout with its right edge. - Verified in the browser at a wide viewport and at both mobile breakpoints. ## Non-goals - The lamp, the nav buttons, the search box and the version readout all stay. - The health board's own layout is not part of this change. --- Depends on: #159
naps62-yolo added this to the Feedback pass milestone 2026-08-24 11:23:47 +01:00
naps62-yolo added the difficulty/easyphase/5-uitype/chorearea/web labels 2026-08-24 11:23:47 +01:00
naps62-yolo added a new dependency 2026-08-24 11:23:53 +01:00
#159 Amend DESIGN.md for the feedback pass
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
arr-api
 area/ci
CI and test harness
 area/compat
arr-compat
 area/core
arr-core
 area/daemon
arr-daemon
 area/db
arr-db
 area/dl
arr-dl
 area/indexer
arr-indexer
 area/infra
workspace and tooling
 area/meta
arr-meta
 area/parse
arr-parse
 area/probe
arr-probe
 area/subs
arr-subs crate: providers, extraction, translation, sync
 area/web
web/
 difficulty/easy
bounded, obvious approach, few files
 difficulty/hard
subtle correctness or cross-cutting
 difficulty/moderate
multiple files, judgement, an interface to design
 difficulty/trivial
one file, mechanical, no design decisions
 phase/1-skeleton
workspace, CI, config, database, empty API and SPA
 phase/2-logic
parsing and policy engine, pure, no network
 phase/3-sourcing
TMDB and Prowlarr, read-only
 phase/4-movies
movies end to end
 phase/5-ui
search, buckets, library views, queues
 phase/6-tv
seasons, episodes, tracking, derived status
 phase/7-people
owner tags and notifications
 phase/8-compat
Jellyseerr shim
 phase/9-subtitles
build order: subtitles, DESIGN.md §15
 type/bug
type/chore
type/feature
type/test
No Label area/web difficulty/easy phase/5-ui type/chore
Milestone
No items
No Milestone Feedback pass
Projects
Clear projects
No project
Assignees
Clear assignees
hermes (Hermes (agent)) naps62 (Miguel Palhas) naps62-yolo (naps62-yolo (agent))
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Depends on
#159 Amend DESIGN.md for the feedback pass
yolo/arr
Reference: yolo/arr#166
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?