Hi John, As a follow up from our meeting this morning regarding Bug 637455, we need to create a template that we can use for First Run for FX5 Beta and one we can use future Beta releases. We can use this template per your recommendation. http://www.intothefuzz.com/leetom/Mozilla.com/JPG/firstrun_11.jpg On the right hand side, we can make the bullets link to be the following: 1. See the New Features (which will link to the channel blog) 2. Participate & Give us Feedback (Link to the happy/sad page) http://input.mozilla.com/en-US/happy http://input.mozilla.com/en-US/sad (checking to see if there's a happy & sad in one page. 3. Check Our the Firefox Channel Page (link to http://www.mozilla.com/en-US/firefox/channel/) We probably need to polish the copy and the icons. But hope that's enough to get us started. Please let me know if I can provide more info. Thanks!

Thanks Grace. Do you mind filing copy & design bugs and making them dependencies for this one? In the copy bug, we should discuss what the message in the main copy area should be, as well as other content considerations like what to do with the newsletter field. Do we change that to a signup for the channel newsletter?

(In reply to comment #1) > Thanks Grace. Do you mind filing copy & design bugs and making them > dependencies for this one? > > In the copy bug, we should discuss what the message in the main copy area > should be, as well as other content considerations like what to do with the > newsletter field. Do we change that to a signup for the channel newsletter? Copy: Bug 652249 Design: Bug 652253

hi john. here is the final design from bug 652253 http://intothefuzz.com/leetom/Mozilla.com/PSD/firstrun_Fx5Beta01.psd Is there anything else we need? are we all set here? who should I assign the bug to? thanks!

Laura, can you assign this bug to the right person? Maybe Steven? Grace, we need this live by the 17th, yes?

Since this is a P1 I'm adding this to the 2.4 release scheduled for 5/10 to give Steven plenty of time to get started. JPG for reference: http://intothefuzz.com/leetom/Mozilla.com/JPG/firstrun_Fx5Beta_03.jpg

17th.

heads up, running into a product issue and the feedback button might not work. please hold further website update until further notice. we are waiting to see if the feedback button will actually work for this coming beta release. in the meantime, we are also getting a plan b design if it doesnt get resolve in time. thanks

(In reply to comment #7) > heads up, running into a product issue and the feedback button might not work. > please hold further website update until further notice. > > we are waiting to see if the feedback button will actually work for this coming > beta release. in the meantime, we are also getting a plan b design if it doesnt > get resolve in time. > > thanks hi all. feedback button is good to go. please use this jpg (same as what was previously provided) http://intothefuzz.com/leetom/Mozilla.com/JPG/firstrun_Fx5Beta_03.jpg thanks!!

What should the URL for this page be? /firefox/5.0b1/firstrun/ or is the beta number something we're avoiding? (still might need it in the URL). Thanks.

(In reply to comment #9) > What should the URL for this page be? /firefox/5.0b1/firstrun/ or is the > beta number something we're avoiding? (still might need it in the URL). > Thanks. hi steven, the url will be: http://www.mozilla.com/en-US/firefox/5.0/firstrun/ please be aware that this link is currently redirected to a blog post. do you need me to file another bug to stop redirect on the 17th? to summarize, comes 17th of may, this will be the link for first run and we should see this new design: http://intothefuzz.com/leetom/Mozilla.com/JPG/firstrun_Fx5Beta_03.jpg steven, let me know if you have any additional questions.

This page is setup in trunk in r88503 (and some images in r88505). The redirect to the blog post was removed from .htaccess in trunk in r88504. Please review the page and pending feedback, I'll merge to stage: https://www-trunk.stage.mozilla.com/en-US/firefox/5.0/firstrun/ Please note that the screenshot and text were mac specific. I added screenshots for Linux and Windows and updated the text for Windows users (where they have to click the Firefox button first). So, for windows users, the feature paragraph starts with "Click the Firefox button, go to the Help menu..."

Thanks Steven. It's hard to preview this b/c the redirect mentioned in comment #10 is still in effect. Any suggestions?

(In reply to comment #12) > Thanks Steven. It's hard to preview this b/c the redirect mentioned in > comment #10 is still in effect. Any suggestions? John, the redirect should be gone - if it's still happening for you, try appending some non-sense URL var to get around a chached redirect: https://www-trunk.stage.mozilla.com/en-US/firefox/5.0/firstrun/?asdf Grace pointed out on IRC that I may have built out the wrong feature images. I was looking here, but I think this file might be out-of-date: http://intothefuzz.com/leetom/Mozilla.com/PSD/firstrun_Fx5Beta01.psd Lee, can you post the lastest PSD? Thanks.

(In reply to comment #13) > (In reply to comment #12) > > Thanks Steven. It's hard to preview this b/c the redirect mentioned in > > comment #10 is still in effect. Any suggestions? > > John, the redirect should be gone - if it's still happening for you, try > appending some non-sense URL var to get around a chached redirect: > > https://www-trunk.stage.mozilla.com/en-US/firefox/5.0/firstrun/?asdf > > Grace pointed out on IRC that I may have built out the wrong feature images. > I was looking here, but I think this file might be out-of-date: > http://intothefuzz.com/leetom/Mozilla.com/PSD/firstrun_Fx5Beta01.psd > > Lee, can you post the lastest PSD? Thanks. i think this is the latest psd: > http://intothefuzz.com/leetom/Mozilla.com/PSD/firstrun_Fx5Beta01.psd (from bug 652253) the mobile promo box should also link to firefox.com/mobile. thanks!

Yep, I think the file in comment #14 is the correct one. Lee, can you review & advise?

http://intothefuzz.com/leetom/Mozilla.com/PSD/firstrun_Fx5Beta01.psd ...should be the latest file. There are 2 feature images here, and maybe the one Grace wanted to start with was turned off. There is the FEEDBACK feature, and also the HELP feature, in case the Feedback button was not implemented yet?

(In reply to comment #16) > http://intothefuzz.com/leetom/Mozilla.com/PSD/firstrun_Fx5Beta01.psd > > ...should be the latest file. There are 2 feature images here, and maybe the > one Grace wanted to start with was turned off. There is the FEEDBACK > feature, and also the HELP feature, in case the Feedback button was not > implemented yet? Thanks. Is there any confirmation yet on the Feedback vs. Help feature, or should I implement both and have them both ready?

(In reply to comment #17) > (In reply to comment #16) > > http://intothefuzz.com/leetom/Mozilla.com/PSD/firstrun_Fx5Beta01.psd > > > > ...should be the latest file. There are 2 feature images here, and maybe the > > one Grace wanted to start with was turned off. There is the FEEDBACK > > feature, and also the HELP feature, in case the Feedback button was not > > implemented yet? > > Thanks. Is there any confirmation yet on the Feedback vs. Help feature, or > should I implement both and have them both ready? the feedback button should be good to go. but is it possible to implement both as back up? in the meantime, i will also double confirm that feedback button is good to go. thanks

Updated the page with the Beta content and Feedback button feature text/images from the up-to-date PSD in r88578.

Grace, can you confirm that the page looks as it should now? I'd like to pass this on to QA.

(In reply to comment #20) > Grace, can you confirm that the page looks as it should now? I'd like to > pass this on to QA. good to go with the feedback button! thanks steven!

Ok, this is all merged to stage in r However, for it to actually show up on stage, we'll have to update the .htacecss file as was done in trunk in r88504. I didn't merge the .htaccess change to stage yet as I wanted to confirm here first. This merge would stop the direct from mozilla.com/firefox/5.0/firstrun and mozilla.com/firefox/5.0/whatsnew to the developer.mozilla.org page from Bug 652124. Is that correct? Also, does there need to be a whatsnew page for the Fx5 Beta, or just this firstrun?

(In reply to comment #22) > Ok, this is all merged to stage in r > > However, for it to actually show up on stage, we'll have to update the > .htacecss file as was done in trunk in r88504. > > I didn't merge the .htaccess change to stage yet as I wanted to confirm here > first. > > This merge would stop the direct from mozilla.com/firefox/5.0/firstrun and > mozilla.com/firefox/5.0/whatsnew to the developer.mozilla.org page from Bug > 652124. Is that correct? yes. this new design will replace the redirect to the blog post (when desktop beta goes live next week) > > Also, does there need to be a whatsnew page for the Fx5 Beta, or just this > firstrun? - just first run one more request: can we update the rapid release blog text to " future releases blog" (name of the new blog) thanks steven!

(In reply to comment #23) > (In reply to comment #22) > > Ok, this is all merged to stage in r > > > > However, for it to actually show up on stage, we'll have to update the > > .htacecss file as was done in trunk in r88504. > > > > I didn't merge the .htaccess change to stage yet as I wanted to confirm here > > first. > > > > This merge would stop the direct from mozilla.com/firefox/5.0/firstrun and > > mozilla.com/firefox/5.0/whatsnew to the developer.mozilla.org page from Bug > > 652124. Is that correct? > yes. this new design will replace the redirect to the blog post (when > desktop beta goes live next week) > > > > > Also, does there need to be a whatsnew page for the Fx5 Beta, or just this > > firstrun? > - just first run > > one more request: can we update the rapid release blog text to " future > releases blog" (name of the new blog) (ignore this last comment. confused from the blog bug.) > > thanks steven!

Ok, the .htaccess file has been merged to stage now too (in r88694). Reader for QA: http://www.stage.mozilla.com/en-US/firefox/5.0/firstrun/

(In reply to comment #25) > Ok, the .htaccess file has been merged to stage now too (in r88694). > > Reader for QA: http://www.stage.mozilla.com/en-US/firefox/5.0/firstrun/ hi steven. thanks! the page looks a bit funny with my 4.0.1 (see attachment). The channels promo is in another column (below newsletter and mobile promo. tried the link in aurora and it looks fine.

Addressed Grace's issue in trunk in r88698 and merged to stage in r88701.

(In reply to comment #28) > Addressed Grace's issue in trunk in r88698 and merged to stage in r88701. hi steven. thanks for updating that. Just a follow up from our earlier conversation, can you please confirm that the headline will say "You are now running Firefox Beta" per the design vs. what it says currently (also in the screenshot attached) "You're running an unknown version of Firefox" thanks!

Issue from comment #29 is fixed in trunk in r88714 and merged to stage in r88715.

thanks steven!

hi steven, what's the next steps here? can we push live today? also just to confirm per your comment 22, the /whatsnew page will also redirect to this new /firstrun page?

qa-verified-trunk https://www-trunk.stage.mozilla.com/en-US/firefox/5.0/firstrun/

(In reply to comment #32) > hi steven, what's the next steps here? can we push live today? also just to > confirm per your comment 22, the /whatsnew page will also redirect to this > new /firstrun page? - opened a bug for the redirect: https://bugzilla.mozilla.org/show_bug.cgi?id=657481 - ignore request on pushing live today. i remembered why we didnt want to push it now and wanted to wait until Thursday 5/19 (as we are using mozilla.com/firefox/5.0/firstrun for 5.0b1 firstrun as well) sorry for the confusion.

reopening bug and assigning to Christian to push. Steven, Christian will push the page. thanks! Christian, this bug is still dependent on bug 657481 (whatsnew page to firstrun page). other than that, should be good to go.

I should push this one. Christian only pushes updates to product-details. Bugs can be RESOLVED before they are pushed.

Can we push all these now? Seems like they will just be sitting there until loaded by the build. Also, please note I moved them into 5.0beta in rev 89103

Pushed live in r89153 and r89157

verified fixed https://www.mozilla.com/en-US/firefox/5.0/firstrun/