This round we focused on: • Exploring navigation layouts and where to place the Mozilla tab on the main site and sub sites.
• Exploring IA and naming of the navigation links and thinking of how to simplify the About section.
• Updating the wireframes based on the feedback we heard last time, including adding in the messaging and more manifesto elements on the landing pages.
Having "Get Involved" in the navigation comes down to how strongly we need it here to tell our community story. Can we do a good enough job across other pages (+ link in the footer) to communicate that we have a dedicated community that you can join?
Also, I’d argue, that this competes (and could confuse the user) with the Advocacy section since we ask users to take action there. I see the current “Get Involved/Contribute” page more about becoming a Mozillian. Advocacy would ultimately contain lower barrier, issue-specific, tasks that can be completed right away w/out commitment.
We can test the option 1 nav with 5 items as well as the 6 item nav shown here.
I think it’s great that you explored this. There are a couple of reasons why this would be challenging. This will make the navigation a little more complex since Policy/advocacy and Education have a sub-nav of their own. Also, having advocacy and education in the global nav will help to tell our story faster, rather that rely on a user to click into “Mission” to discover them.
+1 to removing Tabzilla on homepage, but still allowing space in the template so that when it is introduced, there is space for it.
I like exploring not having tabzilla when it would be redundant, but there being an obvious system to when/why it is displayed.
With 2 logos here we run into space issues on small viewports. Especially in languages with typically higher character volume. It may not look like an issue when considering the 3 global nav items, but there is a sub-nav that has more items in it that is left aligned with the global nav items. Open to exploring this, but it would be the first challenge to consider.
I am unsure what the CTA at the top of this page would do. I think we want to drive the users attention and participation to the content in the left/tert navigation and differentiate this template from the landing page template.
I'd recommend doing the following:
- minimizing the top part of this page
- keep the intro copy
- remove the CTA
- focus on getting users' attention on actionable page content within tert nav items.
By minimizing the to part of the page, it both further differentiates it from the landing page template (e.g., P&A landing page) and drives users towards interacting with items in the left/tert nav.
One way this page differs from the Advocacy page is that we want to drive the users to the Education initiatives... On the Advocacy page we also propose an action the user can take like signing a petition. On this page, there is no need for 2 links (button + link) in the content blocks. The primary, and only action in the blocks is to link straight to Webmaker, MDN, and Mozfest.
Created on 06/04/2015 at 06:40 PM
Get Feedback On Your Work
Notebooks allows you to quickly collect feedback in context. Click and drag on the screen to leave an annotation.
Collaborate With Your Team
Leaving notes for yourself? Talking into an empty room? Are you crazy?! Notebooks lets your team collaborate via sharing.
Great, now get in there and try it out!
Use the sample project provided here to get a “feel” for how Notebooks works. Leave two annotations to complete the demo.