Skip to content

naming: 'Safe content' doesn't say what it is — rename, and open the authoring page to more content kinds #149

Description

@genwave-radio

From docs/THOUGHTS.md.

"Safe content" made sense from the inside (never-dead-air safety net) but conveys nothing to a new operator — safe from what? It's really station-maintenance audio. Consider renaming (Patter? Station audio? Standby content?) and generalizing the authoring page to other kinds: station IDs, jingles, sweepers — same render→measure→catalog pipeline, different kind tag.

Naming note: whatever wins must stay coherent with the taste-exclusion law (gh-#99: safe content is functional audio, never rateable) — the name should make THAT rule feel obvious too.

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

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions