Global nav links should behave like links

RESOLVED FIXED

Status

RESOLVED FIXED
a year ago
a year ago

People

(Reporter: agibson, Assigned: agibson)

Tracking

Production

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

a year ago
The current global nav behavior on mozorg when clicking a top link (e.g. "Firefox") is to open the side menu and expand the sub navigation.

Several people have reported this as a bit of a confusing experience, and now that we have the sub navigation on pages [1] it also feels somewhat redundant now.

I'd like to propose we change this behavior and just let the links behave like regular links, taking visitors to the main top-level landing section for each page. If people want to navigate straight to a sub-page, they can still use the menu button.

It's also been mentioned that the "Download Firefox" link in the top right is too easy to miss. I think we should style it to be consistent with our regular download buttons.

[1] https://www.mozilla.org/en-US/firefox/
I'd really like to see more qualitative user testing of the site focusing on the key tasks we want users to accomplish. That we don't have random slack conversations full of opinions, we have instead qualitative user testing scores similar to what the onboarding team has been doing.
(Assignee)

Comment 2

a year ago
(In reply to Jeff Griffiths (:canuckistani) (:⚡︎) from comment #1)
> I'd really like to see more qualitative user testing of the site focusing on
> the key tasks we want users to accomplish. That we don't have random slack
> conversations full of opinions, we have instead qualitative user testing
> scores similar to what the onboarding team has been doing.

We're continually testing on the site, the nav included. Thanks

Comment 3

a year ago
Hey Alex,

Let's drop this into our priorities backlog: https://docs.google.com/spreadsheets/d/1fizrZ92kNr6sJSMizxl343OF7F-BCJHEUG5TfWj1Gs8/edit#gid=0

Then we can prioritize it based on effort, potential lift, etc. Then once it is prioritized we can determine if we should A/B test, user test, etc.
(Assignee)

Comment 4

a year ago
(In reply to pgerman from comment #3)
> Hey Alex,
> 
> Let's drop this into our priorities backlog:
> https://docs.google.com/spreadsheets/d/1fizrZ92kNr6sJSMizxl343OF7F-
> BCJHEUG5TfWj1Gs8/edit#gid=0
> 
> Then we can prioritize it based on effort, potential lift, etc. Then once it
> is prioritized we can determine if we should A/B test, user test, etc.

Hey Peter,

This is a simple change - I already have a patch to do it ready. We've had considerable feedback already on the current behavior, but I'd be happy to do some more A/B or user testing on this first if you would like to do that.
Flags: needinfo?(pgerman)
(Assignee)

Comment 5

a year ago
Created attachment 8871339 [details] [review]
GitHub pull request

Initial PR, but do-not-merge for now.
(Assignee)

Updated

a year ago
Assignee: nobody → agibson
Status: NEW → ASSIGNED
(In reply to Alex Gibson [:agibson] from comment #2)
> (In reply to Jeff Griffiths (:canuckistani) (:⚡︎) from comment #1)
> > I'd really like to see more qualitative user testing of the site focusing on
> > the key tasks we want users to accomplish. That we don't have random slack
> > conversations full of opinions, we have instead qualitative user testing
> > scores similar to what the onboarding team has been doing.
> 
> We're continually testing on the site, the nav included. Thanks

I'm aware of optimizely stye quantitative tests. What I've suggested in a few different ways is usertesting.com tests leveraging our user research expertise, similar to the usertesting video tests we've done for onboarding 2.0, where a qualitative user satisfaction score was a key goal. Has this been done?
(Assignee)

Comment 7

a year ago
(In reply to Jeff Griffiths (:canuckistani) (:⚡︎) from comment #6)
> (In reply to Alex Gibson [:agibson] from comment #2)
> > (In reply to Jeff Griffiths (:canuckistani) (:⚡︎) from comment #1)
> > > I'd really like to see more qualitative user testing of the site focusing on
> > > the key tasks we want users to accomplish. That we don't have random slack
> > > conversations full of opinions, we have instead qualitative user testing
> > > scores similar to what the onboarding team has been doing.
> > 
> > We're continually testing on the site, the nav included. Thanks
> 
> I'm aware of optimizely stye quantitative tests. What I've suggested in a
> few different ways is usertesting.com tests leveraging our user research
> expertise, similar to the usertesting video tests we've done for onboarding
> 2.0, where a qualitative user satisfaction score was a key goal. Has this
> been done?

We've used usertesting.com many times in the past too, thanks.
(Assignee)

Comment 8

a year ago
To be specific about the nav, the particular behavior highlighted in this bug was not user tested first - but it was something our UX & design people wanted to try and get feedback on. The current experience was built and shipped with an aim to rapidly test and iterate on. I'm sure our UX person would be happy to talk to you more about this if you would like to continue this conversation outside of the bug.
(Assignee)

Comment 9

a year ago
Hey Christa, I pushed this change to a demo for testing: https://www-demo5.allizom.org/en-US/

Let me know if you need anything else, thanks.
Flags: needinfo?(cseabolt)
agibson - could you please create a /de/ version with the copy here?

https://docs.google.com/document/d/14K1ZtDxS_f70uYIpQEKXagmPbTLq0kK8SL9vy8MJVJY/edit
Flags: needinfo?(agibson)
(Assignee)

Comment 11

a year ago
(In reply to Eric Renaud from comment #10)
> agibson - could you please create a /de/ version with the copy here?
> 
> https://docs.google.com/document/d/
> 14K1ZtDxS_f70uYIpQEKXagmPbTLq0kK8SL9vy8MJVJY/edit

This bug is not for localizing the global nav, I believe that's bug 1363312 which is not underway yet.
Flags: needinfo?(agibson)
Thanks Alex. Per our conversation in Slack, retracting request in comment 10

Updated

a year ago
Flags: needinfo?(pgerman)

Comment 13

a year ago
Commits pushed to master at https://github.com/mozilla/bedrock

https://github.com/mozilla/bedrock/commit/25d9e30c016e11d132fc1549109b6644d378dbed
[fix bug 1367793] Global nav links should behave like links

https://github.com/mozilla/bedrock/commit/b59247b7c68758b6c544cca6aaaa973b0f78947a
Merge pull request #4858 from alexgibson/bug-1367793-global-nav-links

[fix bug 1367793] Global nav links should behave like links

Updated

a year ago
Status: ASSIGNED → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED
(Assignee)

Updated

a year ago
Flags: needinfo?(cseabolt)
(Assignee)

Comment 14

a year ago
This was user tested & approved by Christa - should go out in our next push. Thanks all
You need to log in before you can comment on or make changes to this bug.