Skip to content

Regarding tags #496

@Steve0Greatness

Description

@Steve0Greatness

I don't feel like it's necessary to have 3 tags that will really only ever apply to a single extension: Beepbox, Jummbox, Ultrabox. All of these, from my perspective, will only ever be able to be applicable to Beepbox Extension, as I highly doubt that anyone else would really ever make an extension that would do the exact same thing in this gallery (I might be profoundly uncreative, but I'd tend to think that these tags really only neatly allow for sound playing extensions that can play Beepbox files).

Additionally, the inclusion both "strings" and "text" as tags is a bit redundant, at least in my opinion.

Tags should, in my opinion, be created somewhat conservatively, which is to say that a tag should really only be added if it's applicable to a subset of extensions that people may find useful as a subset. These would be somewhat general tags like "timekeeping," "data management," "user-device interaction," "communications," etc, and probably shouldn't be allowed to be created to sort a specific extension. Rather they should be made with the idea that, even if there's a limited number of extensions under that niche current, (timekeeping as I suggested previously would currently really only apply to Extra Timers) it's general enough to allow for others to actually create extensions that do other things, which still keep under that tag, without retreading trodden ground.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions