Project tags are now editable

Site Feedback
1

We completed GL #1 earlier today, which makes project tag lists editable.

If you edit the game section of a project, you will now see a Tags input which autocompletes from the list of existing tags. E.g.:

image

We have not enabled tag creation this way yet. While it’s technically possible and the backend already supports creating new tags, it’s an open question as to whether and how that should be curated.

The game library docs need to be updated to reflect this change.

2

Done …

3

First off, I think the should be a clean-up of the current tags. We have overlapping tags, such as scale:operational and scale:Operational. Perhaps, the tags should be case-insensitive to avoid such duplicates.

Secondly, I think the set of tags should be expanded. One could think of categories like

  • category:value with values like wargame, card-game, puzzle, word-game, and so on. Inspiration could be BoardGameGeek’s categories (though categories like WWII are best handled via the era: tag).
  • mechanics:value with values like card-driven, hex-grid, deck-building, and so on. Inspiration could be BoardGameGeek’s mechanics categories.
  • bggid:number The games BoardGameGeek identifier. This should of course link to BoardGameGeek.
  • Other, more module-specific tags:
    • automation:value with values like low, medium, high, full, and similar
    • rules:value with values like included, linked, summarised, html, pdf, and similar
    • tutorial:value with values like yes, no, partial, and so on.
    • rule_enforcement:value with values like none, loose, medium, strict, and so on.
    • optional_rules:value with values like none, some, yes, no, etc.
    • scenarios:value with values like none, yes, a number, and so on.

There are probably other useful tags too that I cannot think of off the top of my head.

Ideally, I think registered users should be able to create new tags as they see fit. However, I’m painfully aware that that may lead to chaos quite quickly. Perhaps, ways to limit tags to a more reasonable - and useful - set would be to

  • Define a number of super tags, such as topic, era, subject, scale, category, mechanics, bggid, automation, rules, tutorial, rule_enforcement, optional_rules, scenarios, and so on. This set can only be added to by explicit library maintainer interference.
  • For each of these, except perhaps bggid, library contributors may add new values.
    • Values are always case-insensitive
    • Values can requested, either by adding the super-tag-value combination to a project, or through some dedicated page, and then OK’ed by library maintainers.

Yours,
Christian