every-channel/every.channel
1
0
Fork 0
Code Releases Activity Actions 2
every.channel/evolution/proposals/ECP-0118-broadcast-console-web-presentation.md
every.channel 5d6f77f868
Some checks are pending
ci-gates / checks (push) Waiting to run
Details
deploy-cloudflare / checks (push) Waiting to run
Details
deploy-cloudflare / deploy (push) Blocked by required conditions
Details
Redesign hosted web as broadcast console
2026-05-04 01:06:41 -07:00

1.4 KiB
Raw Blame History

ECP-0118: Broadcast Console Web Presentation

Status: Draft

Problem / context

The hosted web page presented the live player as a technical protocol console: relay URL, broadcast name, WebTransport badge, and diagnostic wording were all first-screen material. That is useful for operators, but it makes the public experience feel like infrastructure instead of television.

Decision

Use a generated 1980s broadcast master-control image as the page backdrop and redesign the first screen around a tuned television surface plus a compact station console. Keep the live player and public stream list visible, but move relay URL, channel key, DVR mode, and share URL into a collapsed "Signal source" drawer.

Consequences

  • The first impression is a premium broadcast console instead of a protocol dashboard.
  • Station discovery remains one click from the first screen.
  • Operator controls are still present for debugging and direct links, but no longer dominate the public page.
  • The generated image is unbranded and contains no readable labels, so it evokes the Sony-era hardware direction without making a visible trademark claim.

Rollout / teardown

Deploy the web asset bundle and validate the hosted page visually in the browser plus the existing watch E2E. Teardown is removing the generated asset, restoring the prior panel layout, and promoting the signal fields back to the first-screen controls.