Skip to content

UI/docs: radio jargon ("bed", "liner", "imaging", "ident", "patter") needs a plain name or a one-line explanation wherever it appears #707

Description

@genwave-radio

Dean (2026-09-06): "either properly explain when using radio terms like bed, etc. or stop using them and call them what they actually are… most self-hosters will not understand those terms out of the box. Bed is not intuitive right away."

Where the words sit today (admin-ui grep)

  • Bed — ads/AdSpotEditor.tsx (field + help), safe-content/BedPicker.tsx (Help: Bed flyover). → "Background music", flyover: "quiet music playing under the voice".
  • Station Imaging — safe-content/page.tsx title, NowPlayingCard.tsx "Station Imaging rotation". → "Station sounds" (or "Jingles & station IDs").
  • Liner — default kind label in safe-content/imaging-kinds.ts. → "Voice liner: a short spoken station line".
  • Ident / patter — settings help keys Station:Imaging:ClockAnchoredIdents, *:PatterCadenceMinutes. → "station ID"; "DJ talk".
  • README / DEPLOYMENT / catalog docs use the same words; the /document pass owns those.

Rule

A radio term appears in the UI only with the plain name first and the jargon once in parentheses — "Background music (bed)" — or not at all; every help flyover carries the one-line definition. Decide rename-vs-explain per term, add the rule to the design skill and CONTRIBUTING so new surfaces inherit it.

Epic: #380 (ads surfaced it; the fix is station-wide)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3Low priorityenhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions