Zayin/Signage
3
0
Fork 0
Code Issues 3 Pull Requests Actions Packages Projects Releases 5 Wiki Activity

Displays panel tells administrators to pair under "Display devices in the Dashboard sidebar", which Core is removing #24

New Issue
Open
opened 2026-10-16 01:37:03 +00:00 by ekklesia-bot · 1 comment
ekklesia-bot commented 2026-10-16 01:37:03 +00:00
Member
Copy Link
Copy Source

What I saw

Core is moving display pairing out of the Dashboard sidebar and into Settings → Displays. The Core PR is the Stage 1 UX cleanup, on branch fix/stage1-ux-review; ADR 0064 records the decision. After it merges, the sidebar contains navigation only: there is no Display devices panel and no pairing-code field there.

Signage still sends administrators to the old place, in two spots:

  • src/ui/panels/DisplaysPanel.tsx:216 (released in Signage 0.1.5):

    Enter its six-digit code under Display devices in the Dashboard sidebar.

  • README.md:145, which describes pairing through the Dashboard "sidebar's Display devices panel".

Impact

  • An administrator following Signage's own instructions looks for something that isn't there anymore.
  • Pairing itself is unaffected. The endpoints and the platform display identity (ADR 0036) are unchanged, and every paired display keeps working. Only the wording is wrong.
  • It affects every installation running released Signage 0.1.5 against a Core that includes ADR 0064.

How to reproduce

  1. Run Core with the change above and Signage 0.1.5.
  2. Open Signage's Displays panel with no displays paired.
  3. The hint says to use "Display devices in the Dashboard sidebar", but the sidebar has no such panel. The pairing form is at Settings → Displays → Add display (/settings/displays).

Suggested fix

  • Change the hint to point to Settings → Displays → Add display. Ideally it should be a link:
    • the Dashboard address is /settings/displays;
    • from a module UI, the host's navigation capability (manifest v9, ADR 0063) can carry a return target;
    • for a v8 module, plain text is enough.
  • Update README.md:145 to match.
  • This fits ROADMAP §5.8 ("Signage becomes the reference module": it uses platform-owned displays and links into Settings), so it could be folded into that work rather than shipped alone.

Not looked at

I didn't check whether other Signage UI text, screenshots or docs refer to the sidebar panel beyond these two lines. I also didn't look at the Signage display roster's own behaviour.

Found by Claude during the Core Stage 1 UX cleanup PR (moving display pairing from the sidebar to Settings → Displays).

## What I saw Core is moving display pairing out of the Dashboard sidebar and into **Settings → Displays**. The Core PR is the Stage 1 UX cleanup, on branch `fix/stage1-ux-review`; ADR 0064 records the decision. After it merges, the sidebar contains navigation only: there is no *Display devices* panel and no pairing-code field there. Signage still sends administrators to the old place, in two spots: - **`src/ui/panels/DisplaysPanel.tsx:216`** (released in Signage 0.1.5): > Enter its six-digit code under Display devices in the Dashboard sidebar. - **`README.md:145`**, which describes pairing through the Dashboard "sidebar's *Display devices* panel". ## Impact - An administrator following Signage's own instructions looks for something that isn't there anymore. - Pairing itself is unaffected. The endpoints and the platform display identity (ADR 0036) are unchanged, and every paired display keeps working. Only the wording is wrong. - It affects every installation running released Signage 0.1.5 against a Core that includes ADR 0064. ## How to reproduce 1. Run Core with the change above and Signage 0.1.5. 2. Open Signage's Displays panel with no displays paired. 3. The hint says to use "Display devices in the Dashboard sidebar", but the sidebar has no such panel. The pairing form is at **Settings → Displays → Add display** (`/settings/displays`). ## Suggested fix - Change the hint to point to **Settings → Displays → Add display**. Ideally it should be a link: - the Dashboard address is `/settings/displays`; - from a module UI, the host's navigation capability (manifest v9, ADR 0063) can carry a return target; - for a v8 module, plain text is enough. - Update `README.md:145` to match. - This fits ROADMAP §5.8 ("Signage becomes the reference module": it uses platform-owned displays and links into Settings), so it could be folded into that work rather than shipped alone. ## Not looked at I didn't check whether other Signage UI text, screenshots or docs refer to the sidebar panel beyond these two lines. I also didn't look at the Signage display roster's own behaviour. --- Found by Claude during the Core Stage 1 UX cleanup PR (moving display pairing from the sidebar to Settings → Displays).
ekklesia-bot added the found-by-claude label 2026-10-16 01:37:03 +00:00
ekklesia-bot commented 2026-10-16 01:42:24 +00:00
Author
Member
Copy Link
Copy Source

The Core change is Zayin/Ekklesia#112 (Zayin/Ekklesia#112). It is open and not merged; the sidebar panel goes away only once it merges.

The Core change is Zayin/Ekklesia#112 (https://git.zayin.net/Zayin/Ekklesia/pulls/112). It is open and not merged; the sidebar panel goes away only once it merges.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
found-by-claude
Found by Claude while working on another task
No labels found-by-claude
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
Joey Zayin_Admin ekklesia-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Zayin/Signage#24