Skip to content

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

Closed
agjohnson opened this issue Jan 5, 2018 · 5 comments
Closed

UX changes around project tags #3476

agjohnson opened this issue Jan 5, 2018 · 5 comments
Labels
Needed: design decision A core team decision is required
Milestone

Comments

@agjohnson
Copy link
Contributor

There are a few issues with project "tags". I've noticed misuse of tags since we started prompting users for these:

  • This overlaps with VCS "tags", something we rely on for versions. We shouldn't continue to introduce this confusion. We could rename "tags" to something else, or could improve the UX around tags
  • I'd say prompting for tags on the dashboard page is a bad pattern. We should consider a more consistent pattern for onboarding if we want to make this an onboarding step. We already have other similar onboarding steps, this should probably be included in that. The listing of "tags" is probably the wrong place to tell users to add them though, as new users don't even know what tags are at the point they are being asked.

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.

@agjohnson agjohnson added the Needed: design decision A core team decision is required label Jan 5, 2018
@agjohnson agjohnson added this to the Admin UX milestone Jan 5, 2018
@stsewd
Copy link
Member

stsewd commented Jan 5, 2018

GitHub uses the word Topics.
What about Keywords?

@RichardLitt
Copy link
Member

Keywords makes the most sense to me. Topics would also work, but I think it is more semantically constrained in scope.

@humitos
Copy link
Member

humitos commented Jan 7, 2018

Maybe a stupid question but, is keywords a meanful word for people that's not technical? I mean, people that it's not a developer, for example (considering that RTD is not just software projects)

To me, not being a native English speaker, keywords it's associated with software and topics has a more general meaning/sense. It invites me to add some words about the content of my docs itself.

@RichardLitt
Copy link
Member

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.

@agjohnson
Copy link
Contributor Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needed: design decision A core team decision is required
Projects
None yet
Development

No branches or pull requests

4 participants