722856 - [3.6] Improve /all-older messaging on page & page title

Status: RESOLVED FIXED

(www.mozilla.org :: General, defect, P1)

Description

[mcbmoz]

Patrick/Laura,

Current Page title on http://www.mozilla.org/en-US/firefox/all-older.html is "Mozilla Firefox 3.6"

3 different recommendations:

*Change page title to have stronger verbiage on the status of the build
*Make this page less discoverable in search results entirely, removing the page title and replacing it with something generic
*Keep page title, but improve the copy, design and user experience to move users over to the latest build, making it less likely they'll download 3.6 at all (degrade that experience)

Currently, the messaging doesn't stand out next to the illustration - users likely don't read and don't click:

Firefox 3.6.x will be maintained with security and stability updates for a short amount of time. All users are strongly encouraged to upgrade to the latest version of Firefox.

Comment 1

[Laura Forrest]

Note that today Rik was able to "downgrade" this site link which was showing up in Google results for "Firefox". That should help remove this link from the top of Google results but I support taking more drastic steps to strongly inform users this is an outdated build.

How about doing both #1 and #3 from your list above, so: changing the title to have stronger verbage and: improving the copy and design to help move people to the most recent version?    

Patrick - let us know your thoughts.

Comment 2

[Patrick Finch]

I agree the experience should change.

#1 - we currently use the imperative, "Download Firefox 3.6" - I think the copy should reflect that this is a deprecated version of Firefox.  That's probably the most important thing.

#3 - other adjustments: I'm struggling to visualise those if we have addressed the apparent CTA at the top of the page, other than to adjust the copy more to explain 3.6's status: that it is an old version of Firefox that we will still maintain for a short period of time.

Comment 3

[mcbmoz]

Attachment: Mockup for Steven to use for implementation

Mockup for Patrick to review and Steven to use for implementation

Comment 4

[mcbmoz]

Patrick,

Before moving to Steven for implementation:

1.) Can you review/sign-off on recommendations in attachment 593504 [details]

2.) Edit this copy and let me know if you'd like for us to ask Matej to review:

Headline: Firefox 3.6 is out of date & depreciated

Copy: We recommend that you update to the latest version, which is 7x faster, crashes less, and don't worry, we'll import your bookmarks and browsing history too!

3.) Approve new page title:

Current: Mozilla Firefox 3.6

Recommended: Mozilla Firefox Web Browser - Easy upgrading from 3.6

Comment 5

[Matej Novak [:matej]]

Happy to jump in if needed; just let me know. My main concern is that people won't know what "deprecated" means in this context. Is there a clearer/friendlier way we could put that?

I would also break up the copy a bit:

We recommend that you upgrade to the latest version, which is up to 7x faster and crashes less. Oh, and don't worry: We'll import your bookmarks and browsing history, too!

Comment 6

[Laura Forrest]

Hi Patrick - Any thoughts here? If not, let's get this live since the changes above will surely help quell the downloads on this page.

Comment 7

[Laura Mesa [:lmesa] [:lvmesa]]

As Patrick is out, I'll take this one. 

The attachment looks good to me. 

I do want to make one sugestion and remove "depreciated" out of the copy altogether. 

What about:
Headline: "Firefox 3.6 is out of date

We recommend that you upgrade to the latest version, which is up to 7x faster and crashes less. Oh, and don't worry: We'll import your bookmarks and browsing history, too!"

Comment 8

[Laura Forrest]

That's fine, thanks for picking this up. 

let's get this over to Dev to publish.

Comment 9

[mcbmoz]

Ping on this Mike, it's damaging to have the copy out there, see http://www.diigo.com/item/image/1981d/u78p

Comment 10

[John Slater]

+1 - would be great to get this taken care of soon.

Comment 11

[Laura Forrest]

Making this a P1 to hopefully be able to get this live, since every day downloads are slipping through this crack.

Comment 12

[Fred Wenzel [:wenzel]]

All right, I made a thing with James' help. (Page title change, copy change, download button, and removed the hero image).

Chrissie will you check if the page looks good?

http://www-dev.allizom.org/en-US/firefox/all-older.html

This is in SVN in r102103. James, can you take a look if I committed any crimes in that code, and otherwise close this? Merci.

Comment 13

[mcbmoz]

Hey Fred, the content isn't showing up differently yet for me on dev. Is it showing up for you?

Comment 14

[Fred Wenzel [:wenzel]]

Side note: I pushed down the download button quite a bit so that it's next to the text. If we want it to look similar to other pages with a button in the top right, we just need to remove that CSS rule.

Comment 15

[Fred Wenzel [:wenzel]]

(In reply to mcbmoz from comment #13)
> Hey Fred, the content isn't showing up differently yet for me on dev. Is it
> showing up for you?

No it's not :-/ I hope it'll auto-update itself in a few minutes. Sorry for the confusion :-/

Comment 16

[Fred Wenzel [:wenzel]]

Chrissie: It's visible now. Force-reload if necessary.

James: looks like I made a new background image for nothing, /img/covehead/divider-main.jpg exists. Whoops.

Comment 17

[mcbmoz]

BOOM! nailed it. Thanks Fred!

Comment 18

[Fred Wenzel [:wenzel]]

(In reply to Fred Wenzel [:wenzel] from comment #16)
> James: looks like I made a new background image for nothing,
> /img/covehead/divider-main.jpg exists. Whoops.

r102108

Comment 19

[James Long (:jlongster)]

(In reply to Fred Wenzel [:wenzel] from comment #12)
> This is in SVN in r102103. James, can you take a look if I committed any
> crimes in that code, and otherwise close this? Merci.

Looks great to me. Good job wrangling the download buttons into submission!

r+

Comment 20

[raymond [:retornam] (inactive)]

(In reply to James Long (:jlongster) from comment #19)
> (In reply to Fred Wenzel [:wenzel] from comment #12)
> > This is in SVN in r102103. James, can you take a look if I committed any
> > crimes in that code, and otherwise close this? Merci.
> 
> Looks great to me. Good job wrangling the download buttons into submission!
> 
> r+

I dont have access to  PPC machine right now to check so I am faking the user agent string. PPC Mac users should not be able to see the advertised upgrade since we have not supported PPC Mac's since Firefox 4

Comment 21

[James Long (:jlongster)]

(In reply to raymond [:retornam] from comment #20)
> (In reply to James Long (:jlongster) from comment #19)
> > (In reply to Fred Wenzel [:wenzel] from comment #12)
> > > This is in SVN in r102103. James, can you take a look if I committed any
> > > crimes in that code, and otherwise close this? Merci.
> > 
> > Looks great to me. Good job wrangling the download buttons into submission!
> > 
> > r+
> 
> I dont have access to  PPC machine right now to check so I am faking the
> user agent string. PPC Mac users should not be able to see the advertised
> upgrade since we have not supported PPC Mac's since Firefox 4

What happens on all of our other sub-pages?

I suspect that this is a problem within product-details and our whole site suffers from this.

Comment 22

[mcbmoz]

James, what subpages are you referring to?

Comment 23

[James Long (:jlongster)]

I was referring to pages like this: https://www-dev.allizom.org/en-US/firefox/features/

I thought retornam was referring to the download button, but I see now he's referring to the upgrade message.

Comment 24

[mcbmoz]

OK, do you think we are good to go here?

Comment 25

[raymond [:retornam] (inactive)]

Hi James,
I was referring to the upgrade message. PPC users who visit the home page are directed to the all older page to download 3.6 since 4.0 and up are not supported on PPC. We need to put in a check for PPC user-agents on the all older page so we do not advertise the upgrade to those users.

Comment 26

[James Long (:jlongster)]

Gotcha, makes sense. Good catch!

Comment 27

[James Long (:jlongster)]

Fixed in r102175. Does it work?

Comment 28

[raymond [:retornam] (inactive)]

Attachment: stageScreenshot

Comment 29

[raymond [:retornam] (inactive)]

Attachment: productionScreenshot

The page stills shows the download button for latest version of Firefox to3.6 PPC users. Re-opening

Comment 30

[James Long (:jlongster)]

(In reply to raymond [:retornam] from comment #29)
> Created attachment 600444 [details]
> productionScreenshot
> 
> The page stills shows the download button for latest version of Firefox
> to3.6 PPC users. Re-opening

Just curious what happens on any of the technology or feature pages. Are the download buttons shown there?

Comment 31

[raymond [:retornam] (inactive)]

(In reply to James Long (:jlongster) from comment #30)
> (In reply to raymond [:retornam] from comment #29)
> > Created attachment 600444 [details]
> > productionScreenshot
> > 
> > The page stills shows the download button for latest version of Firefox
> > to3.6 PPC users. Re-opening
> 
> Just curious what happens on any of the technology or feature pages. Are the
> download buttons shown there?

The download buttons are  there and that is fine. The thing is we redirect PPC users to download 3.6 so advertising the latest build on the /all-older page to PPC users is wrong.

Comment 32

[James Long (:jlongster)]

download button hidden in r102185

Comment 33

[Laura Mesa [:lmesa] [:lvmesa]]

Lfo--

Didn't we decide last week that we'd kill this page?

Comment 34

[raymond [:retornam] (inactive)]

qa-verified-trunk download button is no longer shown http://www-dev.allizom.org/en-US/firefox/all-older.html

Comment 35

[Laura Forrest]

(In reply to Laura Mesa [:lmesa] [:lvmesa] from comment #33)
> Lfo--
> 
> Didn't we decide last week that we'd kill this page?

Yes, but for the 3.6 EOL project, this Upgrade project has been well under way and it's part of that. 

I can open another bug to kill.

Comment 36

[Laura Forrest]

(In reply to raymond [:retornam] from comment #34)
> qa-verified-trunk download button is no longer shown
> http://www-dev.allizom.org/en-US/firefox/all-older.html

I'm getting the download button. Can this go live with the 1.9 release next week?

Comment 37

[James Long (:jlongster)]

(In reply to Laura Forrest from comment #36)
> (In reply to raymond [:retornam] from comment #34)
> > qa-verified-trunk download button is no longer shown
> > http://www-dev.allizom.org/en-US/firefox/all-older.html
> 
> I'm getting the download button. Can this go live with the 1.9 release next
> week?

Huh? You should be getting it. It's just PPC users that shouldn't.

Comment 38

[James Long (:jlongster)]

pushed to production r102618