See final designs in bug 716131. Please include a "no follow" per https://bugzilla.mozilla.org/show_bug.cgi?id=716131#c28. William - can you provide the social media links?

Twitter: twitter.com/firefoxaurora Facebook: facebook.com/firefoxaurora

Final PSDs almost posted - heads up Steven!

It appears that the Aurora downloads do not run through Bouncer (the download buttons provide direct links). Is that going to continue? I also wondered if we could enhance the existing thank-you page to handle this, or if we'll build out a new page. CC:ing James and Anthony for input.

alex and i are looking into getting aurora run through the bouncer. adding alex to provide more details. do we need it to go through the bouncer first prior to getting this page implemented?

Alex - any feedback on Grace's question above? Let us know, or feel free to file any other sort of IT dependency bugs as needed.

Alex...ping?

(In reply to Grace Jimenez :grace from comment #4) > alex and i are looking into getting aurora run through the bouncer. > > adding alex to provide more details. > > do we need it to go through the bouncer first prior to getting this page > implemented? (In reply to Laura Forrest from comment #5) > Alex - any feedback on Grace's question above? Let us know, or feel free to > file any other sort of IT dependency bugs as needed. (In reply to John Slater from comment #6) > Alex...ping? We're putting the download through bouncer at Grace's request (bug 731299). I'm not sure why running the downloads through a tracking system would be a requirement for implementing this page.

Is this page ready for implementation and is there a target go live date? Trying to get a sense of the priority and timing.

Hi Mike, I reopened the design bug to request for the windows version. It would be great if we can get this page implemented sometime soon since it's been open for a while. Alex Keybl, can you please confirm if need the bouncer link to implement this page? and whether we actually go it? Thanks

Hi Mike, Here are the screenshots from ty: https://www.dropbox.com/s/dgufe9inaa5nt6k/Install_Process_Screengrabs.zip Is this sufficient to get the Windows page up as well? Thanks!

PSD can be found here: https://www.dropbox.com/s/66po5rh5wphwjfm/FFx_Aurora_ThankYou.psd

Some initial groundwork for this in SVN trunk in r107901.

This page is setup in trunk. Since this touches the main download process, it could use careful review (SVN r=107901,108072,108073). Try the download button on https://www-dev.allizom.org/en-US/firefox/aurora/ to try it out.

Steven, this looks and functions great. Thanks! I noticed that the tweet button opens a dialog with just the link as the pre-populated message. We should also add some text to make this easy for users to share out with context. Grace, here's a copy option for the pre-populated message: I'm experiencing the Future of Firefox by using Firefox Aurora. Check it out! [Link]

qa-verified-trunk https://www-dev.allizom.org/en-US/products/download.html?product=firefox-16.0a2&os=osx&lang=en-US&channel=fxaurora for layout the tweet button still doesn't have the copy from comment 14

Thanks Raymond. Should I go ahead with the tweet text from comment #14?

(In reply to Steven Garrity from comment #16) > Thanks Raymond. Should I go ahead with the tweet text from comment #14? Yes. Grace says this copy is approved.

Sorry for the long time to review. Review comments: r108073 is ok because it's only images. r108072 is difficult to read because of a lot of whitespace changes. Including download.old.js on download.html seems sub-optimal. download.js is already there and the current download.html page knows how to serve different locales. Why are you including download.old.js?

Added the tweet text in r108226.

(In reply to Anthony Ricaud (:rik) from comment #18) > Review comments: r108073 is ok because it's only images. r108072 is > difficult to read because of a lot of whitespace changes. Here's a whitespace-free diff: https://gist.github.com/3335432 > Including download.old.js on download.html seems sub-optimal. download.js is > already there and the current download.html page knows how to serve > different locales. Why are you including download.old.js? Yeah, this isn't ideal, but the getDownloadURLForAuroraForLanguage() function is needed on this page now, and is only in download.old.js. I thought of copying it to download.js, but that seemed just as bad, or worse.

Steven, what are the next steps to getting this live? Does this need more review?

(In reply to Mike Alexis [:malexis] from comment #21) > Steven, what are the next steps to getting this live? Does this need more > review? Needs review from Rik.

With the stub installer project, we might move Aurora through Bouncer and that might make this is a smaller project. We need confirmation on this.

Can we resolve this as wontfix?

I've noticed there are 3 dependency bugs here. How can we resolve this?

Reviving this bug, as we have changes in trunk that are causing problems staying in sync with stage/production. I understand we'll eventually be transitioning all downloads to run through the /firefox/new/ page rather than the download.html page. cmore, do you know how far out that change might be? Should we still make changes to download.html to pass Aurora downloads through it, or should that wait and somehow be part of /firefox/new/? Will Aurora ever use the /firefox/new download process?

(In reply to Steven Garrity [:sgarrity] from comment #26) > Reviving this bug, as we have changes in trunk that are causing problems > staying in sync with stage/production. > > I understand we'll eventually be transitioning all downloads to run through > the /firefox/new/ page rather than the download.html page. cmore, do you > know how far out that change might be? Should we still make changes to > download.html to pass Aurora downloads through it, or should that wait and > somehow be part of /firefox/new/? > > Will Aurora ever use the /firefox/new download process? Hmmm, I am almost leaning forward /firefox/new/ (or /firefox/download/) to be the unified release channel page. Beta, aurora, and nightly buttons will probably only exist on their product pages directly and shouldn't point to /firefox/new/ or download.html. How about instead of pointing Aurora to the download.html page that we just make the button point directly to the installer like it is on this page: http://www.mozilla.org/en-US/firefox/installer-help/ Also, in the future when release channel bedrock buttons point directly to /firefox/new/#download-fx/ (instead of download.html) that we should use force_direct=True for non-release channel bedrock download buttons. This way, we can still use bedrock buttons for non-release channels, but we don't have to make /firefox/new/ handle all channels since the release channel is the most important and largest audience. Thoughts?

(In reply to Chris More [:cmore] from comment #27) > How about instead of pointing Aurora to the download.html page that we just > make the button point directly to the installer like it is on this page: > http://www.mozilla.org/en-US/firefox/installer-help/ That's fine with me. If we go this route, we can just wontfix this bug, as that is the current behaviour. This thank-you page for Aurora downloads seems to have originally been conceived and designed over in Bug 716131. cmore, can you make that decision? > Also, in the future when release channel bedrock buttons point directly to > /firefox/new/#download-fx/ (instead of download.html) that we should use > force_direct=True for non-release channel bedrock download buttons. This > way, we can still use bedrock buttons for non-release channels, but we don't > have to make /firefox/new/ handle all channels since the release channel is > the most important and largest audience. That sounds good. The Beta channel does use the /products/download.html thank-you page right now, so that could be considered a "regression". I'm not sure if non-release-channel downloads need that second download page or not. My understanding is that it was originally wanted to help with metrics.

(In reply to Steven Garrity [:sgarrity] from comment #28) > That sounds good. The Beta channel does use the /products/download.html > thank-you page right now, so that could be considered a "regression". I'm > not sure if non-release-channel downloads need that second download page or > not. My understanding is that it was originally wanted to help with metrics. How hard would it be to support non-release channels on /firefox/new/? Sending people to /firefox/new/?channel=aurora would work, and having all of the tracking mechanisms and instructions would be a nice thing for any download I think. We could switch to a dark theme and change the icons for aurora and nightly even. Whether we do that or not, we should come up with a plan for organizing the non-release download paths? Is such a thing a part of the Fx family stuff? It all seems quite confusing at the moment, and it seems that with a plan we might make things easier for users and we developers.

(In reply to Paul McLanahan [:pmac] from comment #29) > (In reply to Steven Garrity [:sgarrity] from comment #28) > > That sounds good. The Beta channel does use the /products/download.html > > thank-you page right now, so that could be considered a "regression". I'm > > not sure if non-release-channel downloads need that second download page or > > not. My understanding is that it was originally wanted to help with metrics. > > How hard would it be to support non-release channels on /firefox/new/? > Sending people to /firefox/new/?channel=aurora would work, and having all of > the tracking mechanisms and instructions would be a nice thing for any > download I think. We could switch to a dark theme and change the icons for > aurora and nightly even. > > Whether we do that or not, we should come up with a plan for organizing the > non-release download paths? Is such a thing a part of the Fx family stuff? > It all seems quite confusing at the moment, and it seems that with a plan we > might make things easier for users and we developers. It shouldn't be too hard to make the unified page handle not release. I would just worry about making the page any heavier with more CSS/JS and call to actions for non-release channels. Regardless of what we do with non-release channels, we should discuss a comprehensive strategy. Maybe something similar to the current bedrock channel page http://www.mozilla.org/en-US/firefox/channel/

Resolving WONTFIX but please reopen if this is still valid.