796204 - Update Plugin Check Site Design

Status: RESOLVED FIXED

(Marketing :: Design, task)

Description

[:ibai]

Attachment: Notes over actual design

The Plugin Check site hasn't been updated in a while and it represents a good amount of UX challenges. There's a working group to update it and we need a updated UI to match the new Sandstone standard. Crystal from UX has made some recommendations that we will like to incorporate to the new design.

Let me or Crystal know if you have questions about the design and we can work together to clarify. 

Thanks in advance.

Changelog:
- Update to Sandstone.
- Update the copy of the introduction to make it less jargon-y (third party plugins). 
- Show the Firefox Download button only when the browser is outdated or the site is access with a different browser (Chrome, IE, Opera, etc). At the moment it shows us for everyone and is distracting. 
- Move the Firefox Download button to somewhere less "visible"/the bottom. The goal of the site is to update the plugins. Firefox Updates are triggered in other places too. We don't want to lose the opportunity to update the Plugins because users jump directly to updating the whole browser.
- Plugin status represented as: 
-- Green Check mark (not clickable) for Up To date plugins: Users don't need to perform any action with this items.
-- Red button for plugins that need to be updated: Users NEED to update them.
-- Blue button for plugins that need to be researched (we don't know their status). It may be ok for the users not to do anything with these plugins.
- Create and Move updated plugins to a new section at the bottom of the ones that need action.
- Make the "Potentially risky plugins" message more visible.
- Remove sidebar
- One help link at the bottom of the plugin update section.
- Move the "join the newsletter" to the bottom of the page.

Comment 1

[Tara (musingt)]

Handing this one to Lee. 
What is your desired timing and priority level on this?

Comment 2

[:ibai]

Can we aim to have this ready by the End of October? It's a medium priority, the site is not broken but we need to update it.

Comment 3

[John Slater]

That timing sounds reasonable, at least from the design perspective. The web prod team will need an implementation bug to get this on their radar.

Ibai, can you file a mozilla.org bug and then make this one a blocker for it? That way the two elements will be linked together, and the web prod team will be able to plan for it.

Thanks!

Comment 4

[:ibai]

Just checking, is there any progress here? 

Thanks!

Comment 5

[Lee Tom]

Hello Ibai, I'm working on this right now - hopefully will have something for you to look at tomorrow. Stay tuned!

Comment 6

[Lee Tom]

Attachment: Firefox Plugin Check - 01

Attaching first mockup for review

Comment 7

[John Slater]

Wow, this looks a lot better...nice work Lee.

I will leave the detailed review to Ibai, who knows the content best, but I like what I'm seeing here.

Comment 8

[Crystal Beasley [:skinny, :crystal]]

(In reply to Lee Tom from comment #6)
> Created attachment 677190 [details]
> Firefox Plugin Check - 01
> 
> Attaching first mockup for review

It's about elebenty million times better!! Can we make the green [up to date] buttons not be buttons? You can't click on them anyway, right?

Comment 9

[Lee Tom]

Thanks Crystal! I can certainly change the green up-to-date buttons to an inactive grey. Before I make these changes, Ibai - do you have any immediate concerns or suggestions?

Comment 10

[:ibai]

This is great!! Thanks a lot for the work.

As Crystal mentions we should remove the distraction of the green "buttons" so a grey sounds perfect. Also, IIRC, the Download button will only show up if the Firefox version itself is out of date, correct?

Once we finish this we can go to the next stage.

This is going to be a nice Xmas gift ;)

Comment 11

[Lee Tom]

Attachment: Firefox Plugin Check - 02 & PSD

Here's another quick mockup to see how the page has shaped up. Merry Xmas! 

PSD is linked here:
http://cl.ly/2y2s2S2n0C2J

Comment 12

[:ibai]

Sweet. Thanks for the quick follow up.

This is what we need. I followed up with the web dev team and we should have this implemented soon.

I will reopen the bug if anything is needed.