Clicking on a badge, reveals the description for that badge. It seems that if a description doesn't exist then the badge disappears.
I tested this with Curious Contributor. Clicking on it reveals the description.
Clicking on Red Hatter, causes the badge to disappear.
Deanna, I know more tweaking is coming, so please excuse any redundant suggestions. Concerning badges:
* badges appear in a couple of places, and the behavior I describe would not be the same for each, so I will be specific about the location
* on the user's profile, where badges are in a horizontal line - mouse rollover should display the badge name. Only the badge name, no description here. The user should not have to go to the full badge screen to see the labels for the badges they have. Most of the time, the number of badges they have will probably fit on that first line. Only when they are really interested in seeing all the possible badges would they go to the full screen.
* that last comment is important - that profile line of badges should display enough fundamental info that satisfies the user's basic need for information about them, so that they do not have to go to the full screen (which could be considered as a distraction from what we want then to do, which is go make and respond to postings.)
* on the full badge screen, though, where the badges are already titled, mouse rollover should display the description. Clicking on the badge should NOT be necessary. For me, it took me a minute to understand what the description was, because that was not what I expected to see by clicking on a badge. Not that I was expecting anything else, but I think interfaces have trained us that descriptions are always seen using mouseover text, not clicking through.
* Clicking through any object expects "drill-down" detail, not just a description. Drill-down for a badge could show (if this is even important to do - maybe not) things like how they got it, where they got it, how many others have it. Although, all that may be overkill or an unecessary distration also.
The wording "Ask a question" is accurate for somescenarios, but it seems odd for starting a non-question conversation or for posting something of interest to all. On first time posting, it made me wonder if I needed to look elsewhere for posting an informational article or starting a conversation.
Maybe the wording could include more? "Submit a query, start a discussion or post a tip..."
Great suggestions @philip_sweany! We will have to explore this further and try to integrate additional verbage around the community.
Recommendation = Add additional wording other than "Ask a Question" to content contribution buttons throughout RHLC.
Submit a Query
Start a Discussion
Post a Tip
In addition to the above I'd like to see:
- Cheatsheet (for a nice short summaries of commands)
- How to (for more in depth guides on how to do something)
- Product News or News (for newsworthy items like when a new version of something is released and what's different)