Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow moderators to directly create tags #180

Closed
cellio opened this issue Sep 21, 2020 · 2 comments · Fixed by #888
Closed

Allow moderators to directly create tags #180

cellio opened this issue Sep 21, 2020 · 2 comments · Fixed by #888
Labels
area: html/css/js Changes to front-end code area: ruby Changes to server-side code complexity: average Not particularly hard, not particularly trivial. hacktoberfest This repo participates in Hacktoberfest. For suitable issues and Hacktoberfest-PRs priority: medium type: change request New feature or request

Comments

@cellio
Copy link
Member

cellio commented Sep 21, 2020

The usual way to create a tag is to add it to a post. This is the path we usually want people to take -- create the tag when you need it, to avoid clutter from speculative tags that never get used. However, there are two use cases I'd like us to support:

  1. Up-front creation of "special" tags. While the meta ones (bug, feature-request, etc) are now seeded, we support the idea of special tags more broadly. If a community wants to have special tags in other categories, they have to first use them and only then add them to the category definition, which isn't always convenient. (Also, older communities don't have the meta seed; I just manually created "support" on Writing and there are only two status- tags there so far.)

  2. Planned tag organization. The Software Development community wanted a set of language tags up front, as a way of channeling people to the right tags, and IIRC Art added them directly to the database. Other communities might, after discussion on their metas and otherwise after due consideration, want to create certain key tags, especially when building out tag hierarchies.

Allowing moderators to create tags before use would address both of these cases. An intuitive place to hook it in would be a (mod-only) "create tag" link on the tags list, though it's ok if it goes in mod tools if that's easier.

@luap42 luap42 added the hacktoberfest This repo participates in Hacktoberfest. For suitable issues and Hacktoberfest-PRs label Oct 3, 2020
@cellio cellio added type: change request New feature or request area: ruby Changes to server-side code area: html/css/js Changes to front-end code complexity: unassessed Needs further developer investigation before complexity/feasibility can be determined. labels Oct 8, 2020
@galegosimpatico
Copy link
Contributor

@luap42
Copy link
Member

luap42 commented Oct 26, 2020

I concur with the assessment of @galegosimpatico here. It’s more important than “nice to have” but (right now) not a deal-breaker. Needs some careful thoughts with regards to UI, but otherwise not too hard. There is already an automatic tag creation tool under /admin/setup FWIW, but limited to admins and some special Meta category tags.

@luap42 luap42 added complexity: average Not particularly hard, not particularly trivial. priority: medium and removed complexity: unassessed Needs further developer investigation before complexity/feasibility can be determined. labels Oct 26, 2020
eip-ewi pushed a commit to eip-ewi/qpixel that referenced this issue Sep 12, 2022
trichoplax pushed a commit to trichoplax/qpixel that referenced this issue Feb 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: html/css/js Changes to front-end code area: ruby Changes to server-side code complexity: average Not particularly hard, not particularly trivial. hacktoberfest This repo participates in Hacktoberfest. For suitable issues and Hacktoberfest-PRs priority: medium type: change request New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants