Increase visibility of Helpfulness Survey at the bottom of Article

RESOLVED FIXED in 2013Q2

Status

support.mozilla.org
Knowledge Base Software
P3
normal
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: ibai, Assigned: rehan)

Tracking

unspecified
2013Q2

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: u=user c=wiki p=1 s=2013.9)

Attachments

(5 attachments)

(Reporter)

Description

5 years ago
Since we added the Share This article box at the bottom of each article, it looks to me that the Helfpulnees Survey has lost "weight" and it's easy to miss (there's no contrast to incentive the call to action).

a) Can we validate that since adding the box we have less votes per visit?
b) Can we add visibility to the Yes and No buttons?

I don't think that a) is a blocker of b). If we can get more votes, it would be a good thing either way.
Created attachment 740632 [details]
helpfulness box - blue highlight - 01
Created attachment 740633 [details]
helpfulness box - yellow highlight - 01
I think the solution is pretty easy: put the helpfulness survey inside a box. Comment 1 and comment 2 contains two color variations of the box, blue and yellow. I like the yellow one the best because it has more contrast.

Also note how the helpfulness survey on the sidebar is enclosed within a darker box. This will help more people find it, so let’s make sure that we do it.

For implementation, the style I was using to create these mockups are the same styles used in div class "note" and class "warning" (but minus the background image on the latter). The sidebar style is class "feature-box" with a reduced margin value of: 10px 20px 15px

Comment 4

5 years ago
Maybe we can dramatically shorten that short link template. Also we can implement that as a feature and design it to fit into the page template taking in to account the overall function of the page.

Comment 5

5 years ago
Created attachment 740810 [details]
Changing the share link template

The share link template is not terribly important. I can change it to reflect that.

Comment 6

5 years ago
Created attachment 740813 [details]
If we implement bit.ly short links as a feature we can design the page better.
(Reporter)

Comment 7

5 years ago
The solution for this last comments is probably the cleanest one. The actual "share link" box is quite verbose. Contributors using it, they already know that the content gets customized and I'm not sure if many non active contributors (i.e. a casual son helping his dad remotely) uses these links.

Thumbs up for Solution on Comment 6?
Thumbs up on comment 6. If our goal is to get more people to click on the helpfulness survey, shortening the share box will be the simplest move to achieve that.

Bonus: shortening the share box will make its intent clearer to people without much fuss. It might lead to more shares.
(Reporter)

Comment 9

5 years ago
Adding this as a candidate for the low hanging fruits that we fix in Q2.
Target Milestone: --- → 2013Q2
Putting into the next sprint for now. Should be easy style fixes. 1pt
Whiteboard: u=user c=wiki p=1 s=2013.9

Comment 11

5 years ago
Created attachment 741448 [details]
New survey design w/ shorter share template

Just to be clear, comment 6 included generating sumo short links through the bit.ly api. I don't think that's something we're going to do right now. So it sounds like this is to put a blue box around the survey and for me to shorten the short link template. That would look like something this attachment.
(Reporter)

Comment 12

5 years ago
Verdi, you are correct. We should simplify the template and then do the API integration further down the road.

Do you want to open another bug with that? It seems that you are more familiar with the API.
(Assignee)

Updated

5 years ago
Assignee: nobody → rdalal
Guessing this is a P3
Priority: -- → P3
(Assignee)

Comment 14

5 years ago
Landed:
https://github.com/mozilla/kitsune/commit/d5b3d9d8b35dff11c94ceae514c4f26f249fde63

Pushed to prod by me, right now.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.