-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
UX changes around project tags #3476
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
Comments
GitHub uses the word |
Keywords makes the most sense to me. Topics would also work, but I think it is more semantically constrained in scope. |
Maybe a stupid question but, is To me, not being a native English speaker, |
Keywords can be used in nontechnical contexts too, yes. The meaning doesn't change much between contexts: salient words which are useful for identifying content. |
On the new dashboard this is not a user editable field on the dashboard, it is only editable on the admin forms. I think that satisfies my needs here, I mostly felt the sidebar form was awkward. I do agree the name could be clearer. I don't love "topics" but that does match GitHub and would probably be my choice if we ever did change it. However, I also feel the name is a minor point in the usability difficulties of project tags. I'll close this issue as I feel this is close enough. |
There are a few issues with project "tags". I've noticed misuse of tags since we started prompting users for these:
There might be some ideas we can borrow from GitHub. Heck, any reason we're not just importing these along with the repository information on import? Obviously this doesn't keep things in sync, but at least seeds our data.
The text was updated successfully, but these errors were encountered: