Closed Bug 481036 Opened 17 years ago Closed 16 years ago

improvements to the beta download page (big download button, clear warning)

Categories

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

Product:
www.mozilla.org
Component:
General
Platform:
x86
All
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: beltzner, Unassigned)

References

(
URL
)

Details

Attachments

(1 file)

All-Beta mockup v1
294.74 KB, image/png
Details
The beta download page (see URL) isn't the friendliest experience for someone looking to download software. We need to do the following: - a brief message like the one we normally use about the intent of the release (for people who want to test, should be stable, not all add-ons may work properly) - a big download button (some colour other than green to differentiate) that works like the one on our main page works - the existing content beneath the fold still there for other languages and systems
Thanks Mike. Steven and I are on it!
Assignee: nobody → jslater
Suggested text for the message: <div id="main-feature"> <h2>Download a beta and help test the future of Firefox!/h2> <p>Firefox 3.1 Beta 2 is available in over 50 languages as a preview release. Help us out by testing and evaluating the <a href="3.1b2/releasenotes/#whatsnew">new features</a>. Note that you may encounter compatibility problems with some websites and Add-Ons. If you find a problem, please <a href="http://feedback.mozilla.org/">let us know</a> or <a href="https://bugzilla.mozilla.org/">file a bug</a>.</p> </div>
Assignee: jslater → nobody
Flags: wanted-firefox3.1+
Target Milestone: --- → 3.0b3
Things to take in account if possible: 1/ The download button should use prefered language detection (like on mozilla.com/en-US/) 2/ ideally, we should be able to bypass the locale detection passing a 'get' argument to the URL like: http://www.mozilla.com/en-US/firefox/all-beta.html?lang=ko
Target Milestone: 3.0b3 → 3.1
Yes, to be clear, I meant for the big download button to work exactly like the one on mozilla.com. Ideally using the same detection mechanisms and code. I want expedience and speed, not creating new and better code.
Steven: download button is committed in r22920 although it has no styling and is just stuck on the page. I put it in it's own <div> so you could see what I added easily. Note that it is also a pain to test due to bug 285267 but I QA'd it with stephend and it is working as well as anywhere else on the site.
Steven noted that the button only shows current released builds. We started tracking betas after this code was written so it has to be changed in the library. I'll file a bug.
Depends on: 481936
Attached image All-Beta mockup v1 —
Hi guys. I've been working with Steven to revise the header of this page to meet the requirements we've been talking about...the first mockup is attached, so take a look and let us know what you think. The final copy will likely change a bit (for example, we need to update the beta 2 reference, or maybe lose it altogether), but this should give you the general idea. Goal was to make the beta feel more accessible to average users while also giving them the proper warnings and explanations of how to report bugs, etc. Lastly, one open issue is localization. If we keep the # of locales pretty limited Pascal said he can get this page localized, too, so the localized start pages will point to localized landing pages. But, we should get this finalized and into SVN pretty soon to make that happen. (note: it's also ok if we stagger the localized versions...the en-US snippet won't come out until a few days after the beta release, and we could then roll out the localized versions as the landing pages become ready.) Anyway, let us know what you think about the mockup.
I like the look of it. I know you said the final copy would change but the only thing I find awkward is the wording of "Download the current released version." I think it should say something about being stable or say "Or maybe you'd prefer the latest stable version" or something like that. I'm not sure people will know what "released" means here.
Awesome. One suggestion: move the "if you find a problem let us know or file a bug" into the main description, and remove the "read the stuff to the right". The stuff to the right is super noticable enough, and I want it to be all warning, nothing else. Sound good? Really great work, guys.
Love it. The fading out of the "Important information" thing is a little odd -- I found myself squinting to see if the 3.0.7 DL link was supposed to be part of it.
(In reply to comment #6) > Steven noted that the button only shows current released builds. We started > tracking betas after this code was written so it has to be changed in the > library. I'll file a bug. Fix is in r22975
I've committed some parts of the mockup (r22977) including Beltzner's suggestion from comment #9. The download button still needs to be styled, and I agree that the bottom of the "Important Information" box is a bit weird. I'll work on improving this. The heading in this box is styled in a way that might break if it ends up on multiple lines in other locales - I'll also need to make this a bit more robust.
Agree that "Important Information" box should exclude the link to 3.0.7 at the bottom -- if textbox just ends it would be nearly even with the bottom of the big download button at left. Also agree with Wil's comment the language of "current released version" is a bit awkward. Maybe use the white space next to the download button for a more generic text link: "Not looking for a Beta? Get the latest Firefox" ...where "latest Firefox" links back to the Firefox download page: http://www.mozilla.com/en-US/firefox/ Lastly, a nit, but in the laundry list of languages and platforms below, we should probably add the word "Beta" to the "Version" column to reinforce and be explicit that "3.1b3" = beta software as on the button above.
Ok, sorry about the delayed comments from me on this. It's looking good, and thanks to everyone for the feedback. We need to get this wrapped up soon so Pascal can start localizing it. I think it's almost there, but let's make the following tweaks first: - fixing the download button logic, obviously (the orange color in the mockup is perfect). - change subhead to reference Beta 3 (instead of Beta 2...typo was my fault) - also, I agree that the copy that now reads "Not looking for a Beta? Get the latest Firefox." (was the bit about "download the latest version") doesn't belong in the Important Information box. What if we put it below the main download button? (below the release notes and other systems & languages line, I suppose) I think this is what Dave was getting at above...seems like a good place for it to me. - if we can make the column say "Beta Version" instead of just "Version" per Dave's comment #13, let's do that too. If that's changing the scope too much, I think it's ok as is. Steven, if you have any questions just let me know. Thanks for your help!
there is a "other systems & languages" link, for en-US, the all-beta page is the "other systems & languages" page since the table is below the box.
It would be good not to have the version number mentionned in the text, more something like "the latest Firefox beta version" than "Firefox Beta 2 is...". This way we will be able to reuse the translation of the page for any future beta version of Firefox witout having to sync with localizers to update the text.
Ok, I've got John's list from comment #14 cleaned up except for the "Beta" wording in the download table. Wil, could we use the product-details tweakString() function to replace "3.1b2" with "3.1 Beta 2" (or beta 3, etc.)? (In reply to comment #15) > there is a "other systems & languages" link, for en-US, the all-beta page is > the "other systems & languages" page since the table is below the box. I've replaced the link with plain text stating: "Other systems and languages listed below.". Wording changes/suggestions are welcome for this.
Also, Wil, it appears the javascript-created version of the download button correctly points at the beta version, but the <noscript> alternative is still pointing to the latest official release.
(In reply to comment #17) > Ok, I've got John's list from comment #14 cleaned up except for the "Beta" > wording in the download table. Wil, could we use the product-details > tweakString() function to replace "3.1b2" with "3.1 Beta 2" (or beta 3, etc.)? Fixed in r23065. I'm using this regex so we don't have to edit the page in the future: '/>([0-9]{1}\.[0-9]{1,2})b([0-9]{1})</' => '>$1 Beta $2<' I don't think it causes any problems but let me know if you notice any. (In reply to comment #18) > Also, Wil, it appears the javascript-created version of the download button > correctly points at the beta version, but the <noscript> alternative is still > pointing to the latest official release. Fixed.
(In reply to comment #16) > It would be good not to have the version number mentionned in the text, more > something like "the latest Firefox beta version" than "Firefox Beta 2 is...". > This way we will be able to reuse the translation of the page for any future > beta version of Firefox witout having to sync with localizers to update the > text. Other folks on this bug - is there any reason why we shouldn't do this? It seems like a good idea to me. I'd recommend saying "The latest beta version of Firefox is now available as a preview release. Take it for a test drive and let us know what you think!" Also, I'm still getting a bunch of stray code below the button on the actual page. Once we fix that and resolve Pascal's question we should be all set. Is the code stuff doable by EOD? If I don't hear any other feedback on Pascal's issue by then let's go ahead and make that change.
Per comment #16 - Yes, I think it makes sense to remove reference to "beta 3" in the subhead text as Pascal suggests, as long as the beta version number is properly referenced on the actual download button and referenced as "3.1b3" in the version column of the chart auto-generated below. (Note: this treatment will still require a change to the logo portion of the download button graphic at beta-4, but at least you won't have to localize subhead text).
Looking great - fwiw, I agree with Shaver's comment 10 that the "Important Information" block feels unbalanced. Can we cap the bottom off with an orange border? I also agree with Pascal: we should avoid referring to the beta number both in the image and the text.
(In reply to comment #22) > Looking great - fwiw, I agree with Shaver's comment 10 that the "Important > Information" block feels unbalanced. Can we cap the bottom off with an orange > border? Sure, that sounds good to me. And let's proceed with the copy change from comment #20 then, too. Steven, let us know when those changes are ready (or if you have any questions). After that, I think this page will be all set for l10n. Thanks all-
I'll get these last few changes done first thing in the AM.
Per Mike's comment to avoid beta number in both "image and text," I want to clarify one point. While I agreed above with Pascal's reco to drop reference to "beta 3" in the subhead text, I do think we must have a "beta 3" reference on the download button. The reason is because we'll link to this page (or press + bloggers will) from other pages that reference "beta-3" specifically (eg. mozilla-home, start page snippet, etc), and it needs to be super-clear to visitors they are downloading the latest/greatest version referred to. Even if we have to swap that image on download button at beta-4, we should keep it, IMO.
The download button is automatically generated so keeping the "Beta 3" text-in-graphics in the download button is not a problem for localizers as they don't touch this part.
I've got all of these changes implemented. I did just notice that I missed beltzner's note in comment #9 to "move the 'if you find a problem let us know or file a bug' into the main description". Should I do that as well?
(In reply to comment #27) > I did just notice that I missed beltzner's note in comment #9 to "move the 'if > you find a problem let us know or file a bug' into the main description". > > Should I do that as well? I think the current "take a test drive and let us know what you think" covers that aspect of the messaging. And like Mike said, the part with more details to the right is pretty obvious. Can I mark this one fixed?
(In reply to comment #28) > Can I mark this one fixed? Not until we push it, I don't think. Soon! Steven: looks great, I think my concerns were addressed in a different way.
the download link is wrong, it displays "unknown" product for me: https://www-trunk.stage.mozilla.com/products/download.html?product=Unknown-3.1b2&os=linux&lang=fr also the release notes lead to 3.0.7
Thanks Pascal, r23124
here is the version I am going to ask localizers to make: https://fr.www-trunk.stage.mozilla.com/fr/firefox/all-beta.html No list of languages since we send there people for which we already did locale detection. Steven, I had to add a css section for locales to all-beta.css and will probably have to add rules to it as the translations are done.
Thanks Pascal. Adding PFinch to the bug. What is the number of locales targeted for localization of this version of the page? Assuming they can also translate the snippet text as well, correct? Patrick can coordinate getting snippets in rotation on the start page after the localized pages are live.
Around 10 locales have already translated the snippet so they are the primary target for the translation of this page.
(In reply to comment #32) > No list of languages since we send there people for which we already did locale > detection. I disagree with this logic. Removing the option to download other languages is inconsistent with the normal Firefox download behaviour, and I think makes likely-but-not-necessarily correct assumptions about the needs and wants of the user. The simplest solution, since we don't want to have to translate the table (which would be a pain), would be to do what we do on the main getfirefox.com site. Beneath the download button, I would retain (and translate): _Release_notes_ (in English) - _Other_systems_and_languages where _Release_notes_ links to the release notes, and _Other_systems_and_languages_ links to en-US/all-beta.html#languages
Mike's latest comment is integrated now, anything else before I give it to localizers?
I assume "in English" is still, uhm, in english because that's up to the localizers to translate, whereas the other strings on that line are generated? Looks great. Thanks, Pascal!
yes, "In English" sounds like a useful string to have in store and reuse for other links so I put it as an external string, it will be translated of course.
Not sure which locales have translated the snippet so far, but from the analysis I ran of Beta downloads versus GA downloads, if all locales came up to the level of en-US Beta testing, 85% of growth in Beta testers would be in these locales (in order of importance): de fr es-ES pt-BR ru pl it ja tr nl Pascal, how does this list compare to those that have already translated the snippet?
Patrick, all of the locales above except Russian have translated the text for the snippet. Our Russian localizer is not online these days. We also have a couple more locales with the snippet done which are not in your list.
Target Milestone: 3.1 → 3.5
Marking this as resolved.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
GoingAwayTomorrowAnyway++ (Verified FIXED.)
Status: RESOLVED → VERIFIED
Component: www.mozilla.org/firefox → www.mozilla.org
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: