656921 - Write copy for out-of-date beta firstrun/whatsnew page

Status: RESOLVED FIXED

(Marketing :: Copy, task)

Description

[Steven Garrity [:sgarrity]]

Matej, we're creating a page that will replace all out-of-date firstrun/whatsnew pages for beta or RC versions of Firefox.

This will be similar to the out-of-date page we redirect people to for final releases: http://www.mozilla.com/en-US/firefox/out-of-date/

See Bug 656721 for more detail. Thanks.

Comment 1

[Matej Novak [:matej]]

Any more direction on what this should say? Specifically, how should it be different from what we already have (apart from mentioning beta and RC)?

Comment 2

[Tara (musingt)]

Hey guys, do you have any additional copy direction for Matej here?  It seems like the edits are small.  Refreshing the copy to reference the version of Firefox they are on (outdated Beta/RC) and pointing to the release channel page for them to upgrade.  Main CTA is not to visit the release channel page and pick a channel to download, right?  Or do we want a download button on this page?  

If you can clarify, Matej can get cracking.

Thanks!

Comment 3

[John Slater]

Tara, your interpretation in comment #2 is basically right, and it's true that the edits are small.

I'd recommend simply changing the existing page a bit to reflect that people are on an old beta/RC, and then include a button to download the current beta. If they're already in the beta channel, let's keep them in that channel (vs sending them to the entire channels page).

Thanks!

Comment 4

[Matej Novak [:matej]]

So should we just add the words "beta" and "release candidate," respectively, after Firefox in the first line?

Thanks for downloading Firefox Beta, but this version is out of date. For the latest security, performance and feature enhancements we strongly recommend that you get the newest version instead.

Thanks for downloading Firefox Release Candidate, but this version is out of date. For the latest security, performance and feature enhancements we strongly recommend that you get the newest version instead.

Also, should it say Mozilla before Firefox?

Comment 5

[John Slater]

I think it's a little more than that, actually, b/c the beta messaging is different than the regular release messaging. Let's talk in person today.

Comment 6

[Matej Novak [:matej]]

Just spoke with John. We're thinking we should keep the current language for RC. If they've somehow managed to find an old RC, we should probably point them to the current final release version rather than a more up to date RC, so what we currently have works.

For beta, here's what I came up with:

Thanks for downloading Firefox Beta, but this version is out of date. For the latest cutting edge features still in refinement we strongly recommend that you get the newest beta version instead.

Comment 7

[John Slater]

The "still in refinement" part is sticking out a bit for me. Think we could drop it? Or reword somehow?

Otherwise looks good, thanks.

Comment 8

[Matej Novak [:matej]]

Sure, here are a few options (the first one just cuts those few words):


Thanks for downloading Firefox Beta, but this version is out of date. For the latest cutting edge features we strongly recommend that you get the newest beta version instead.

Thanks for downloading Firefox Beta, but this version is out of date. For the latest cutting edge features not quite ready for final release we strongly recommend that you get the newest beta version instead.

Thanks for downloading Firefox Beta, but this version is out of date. For the latest cutting edge features and to give relevant feedback we strongly recommend that you get the newest beta version instead.

Comment 9

[John Slater]

Let's just go with the first one...I like the simplicity. Thanks!

Comment 10

[Steven Garrity [:sgarrity]]

Thanks - marking this as FIXED and we'll carry on with implementation in Bug 656721.