I understand, I just don’t agree in this particular case it is our job to teach non developers how to be developers. It is like snowboarders using snowboarding slang, it is signaling to a specific crowd.
I don’t think we are really against this feature, but there is a fair bit of UI work to make anything like this happen.
Some UI mockups of how you feel this should work would be very helpful.
Thanks Sam. Will work on making proper mockups later in the week. One outstanding question is what will happen to tag descriptions if the tag is not used by any topics? Is it possible for the tag to remain listed, or if not, will the description remain when the tag is used again?
the simplest way is just to have a pinned topic on top of the tag pages, which is “about the …-tag”. can’t it work?
I really like this idea! We already have UI for making pinned topics, just
add a button to the existing UI that says “make this topic the description
for xxx tag” with xxx being a tag selection menu.
We’ve recently added tags in large part to help users categorize user-made games, and there’s been a bit of a request for this. Specifically we’ve found that some tags are useful, but people will have a lot of trouble figuring out certain things. For example, I created a handful of tags: 1)
pc-customization, or 2) a set of
The thing is, people could not parse what they meant. There was discussion as to whether
pc-customization meant AFGNCAAP, whether it meant a ‘pick your hair/eye/skin color’ question, or whether it meant any kind of customization at all no matter how small.
Likewise when I made the various fantasy tags, I meant them to distinguish three different types of fantasy, i.e. to be mutually exclusive, but some games were marked with multiples of them. (I know, I should have defined that then, hide sight is 20/20, but still, not the issue at hand).
Is there any appetite for revisiting this in some form?
We’re still in the “ruminating” phase on how we may lean on tags much more heavily than categories going forward (see: Does your community rely heavily on tagging? What tips do you have?).
But this question of whether there’s a way to have descriptions for tags has come up.
As for UX, I see two possibilities:
- The pinned topic idea
(might make sense anyway. it’s more generic and we might pin topics other than the “about” one for a given tag if this feature existed)
- A first class description
(I think this would be better way to add descriptions for tags in the long run)
As for UI, I’m thinking it could be something like a div of text above the topic list with an edit pencil to update it:
I think now that tags are first class entities it is much more appealing, we could keep an extra field here for the description or maybe even allow for a topic per tag like we do for categories.
I do like the idea that you could get a little bit more guidance when tagging and when looking at tags.
I think this might work as an optional thing - requiring a topic for every tag seems a bit overkill, but you could put a link to the topic at the end of the tag description display. (Read more…)
That’s my feeling as well. Granted, I have a very narrow view in terms how different communities are using them. My rough impression is that tags are a magnitude more numerous than categories and a magnitude less in the number of topics they have.
I’m thinking a short (half an old tweet length?) description field as a tooltip would be a good starting point.
I don’t think tag descriptions would ever be long enough to necessitate a topic, even the complicated ones tend to only need a sentence or two of explanation. Adding a description text field to the tag editor would do the trick.
Tag descriptions are useful in Stack Overflow and they would be useful in Discourse as well. Just a sentence or a few words would aid in understanding what tags are about. Here’s are some examples from Stack Overflow:
We have a lot of employees who work with Discourse, and many want to see tags like in Stack Overflow. This is especially important when tags are part of the navigation. If this is added to the core of the site, then this is just great news.
For one of the forums I’m administering, it would also be useful for tags to have tag descriptions (which, in my mind would be available as a tool tip on mouser-over on desktop) because we have a tag for each command that the program takes via the CLI, such as
set. Since it is not immediately obvious why a post would be tagged #set, it would be nice if people could find out.
Having said that my preference would be a fully fledged description field for each tag, here is an idea that might work at least in our case: all CLI commands are in the same tag group called “CLI commands” or so. If each tag group had an option
[ ] prepend tags from this group with _______
So if I’d enter “command” as a prepend string, the #set tag would be displayed as “command:set”
Ah, well, no. It’s probably a lot better with a simple description field.
Just for completeness: another good use case for tag descriptions that can include links is as a place to point out to anonymous visitors that they can subscribe to the tag by RSS (in case they don’t want to sign up just yet …).
Technically RSS for tags works just fine (example), but without a place to point out that feature, users will hardly find it. Except for those with an RSS browser extension.
We do this with category descriptions and would love to do the same with tag-pages. For example, the Web Dev Teams will often need to access our Github, so adding:
Gives them a smoother experience
I would love to see tag descriptions as well. A combination of the description below the tag in /tags along with the description on the tag’s page as Dave posted above would be perfect. We use a few obscure tags that make sense to existing users, but new users struggle to understand. If I were to make the tag long enough to understand it would be unruly in the UI, but if I leave it the way it is, it ends up leading to time wasting questions about what the tag is for.
check this theme:
That just adds a banner, not a description. There is this component to add a tag description, but it’s a little painful to use if you want descriptions for a lot of tags, and I would prefer to have the description up top rather than on the side because it breaks the Topic List Preview plugin.
There are no plans for this, as tags are meant to be lightweight.