Closed Bug 649680 Opened 13 years ago Closed 13 years ago

build default What's New page for Fx 4.0.x

Categories

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

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

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: jslater, Assigned: sgarrity)

References

(
URL
)

Details

When we launched Fx4, we intentionally served up the First Run page to both new and existing users. But, now that we're moving into the dot release phase, we need to branch out and have a separate What's New page again.

The content is being created in bug 644329 and should be complete by the end of the week. After that, we need to get this into the 2.1 release (ideally with at least some initial l10n as well).
will there be a 4.0.2 release? I want to build generic whatsnew pages for l10n reusable for any Firefox version, would it be possible to have this page be the same as the generic one for Fx5/6...?
Good questions - I think those are probably best answered by Mayumi (Mayumi, see comment #1 please).
Ideally we go straight from 4.0.1 to 5 however there is definitely a good chance that we'll have to launch a 4.0.2 between now and 5.  So there is no 4.0.2 planned for now but who knows.  

Regarding the what's new page, the template can definitely last for a very long time well into 6,7,8, etc. And for the content, App Tabs are something that we could keep for some time e.g., 2-3 months however, if you want content that lasts even longer then I suggest promoting Sync in the main top box.
Designs are ready, so am kicking this over to webdev:

http://intothefuzz.com/leetom/Mozilla.com/JPG/whatsnew_03.jpg
http://intothefuzz.com/leetom/Mozilla.com/PSD/whatsnew_01.psd

A few notes:
- this needs be live on April 26
- still working out the l10n strategy, but would like to have the initial code ready to give Pascal some time to work on it. Pascal, let us know what you think re: timing, feasibility, etc
- the screenshot in the PSD isn't final...need one that doesn't use Minefield, of course. Lee, can you do the final Mac one to serve as template for the Linux & Windows versions?
Sure. It would be great to get sign-off on which pages will pinned as App-tabbed, and which page will be open:

apptabs
- Facebook
- Twitter
- Thunderbird? 

open page
- TBD
Mayumi, please weigh in if you feel otherwise, but I'd suggest Gmail and Twitter for the app tabs and some wikipedia page of your choosing for the open page (but don't show the content on the page, of course).
Target Milestone: 2.1 → 2.2
Thanks Lee. Actually, just talked to Mayumi & we decided on Gmail & Twitter for app tabs (like you have now) but nytimes.com for the main tab. Only catch there is that we shouldn't have any date-specific content from that site bleed on to the screenshot.

After that we're all set.
Thanks Lee. Laura, who can we assign this to?
This needs to be live by April 26th.
Assignee: nobody → steven
Priority: -- → P1
Pascal, any further thoughts on l10n prospects?
Priority: P1 → --
Where should this page live? /firefox/4.0/whatsnew/ or does it have to be separate from that page (/firefox/4.0.x/whatsnew/)?
(In reply to comment #13)
> Where should this page live? /firefox/4.0/whatsnew/ or does it have to be
> separate from that page (/firefox/4.0.x/whatsnew/)?

It should follow the same convention we do with the other What's New pages, where we differentiate by version number. Since this is sort of the default, starting off at /4.0/whatsnew/ seems right...what do you think?
Should this page include the out-of-date Flash plugin warning that we had in the 3.6 whatsnew page? (this was not included in the current 4.0 page, as far as I can tell).
(In reply to comment #15)
> Should this page include the out-of-date Flash plugin warning that we had in
> the 3.6 whatsnew page? (this was not included in the current 4.0 page, as far
> as I can tell).

I don't think so, but Mayumi should weigh in. I can't find the bug but remember that we didn't include it in 4.0 bc that issue is fairly old, and is not currently a huge issue, esp. w/Fx4. 

Mayumi?
Mayumi, Steven and I had series of IM conversations about this...here's the basic update:

- we definitely want this page to have the Flash warning functionality
- we want to make some changes to the wording and possibly design to make it more clear that the problem lies with Flash, not Firefox (don't want people to think that Firefox is fundamentally insecure)
- Steven is going to start building the page with the Flash warning in mind, but we may turn it off at first while we make those tweaks (will file a spinoff bug for the tweaks)
Blocks: 651958
Filed bug 651958 for the Flash warning tweaks (but it shouldn't block this one).
On a separate note on this design to consider for next time: it would be
helpful to provide a link for people to learn more about app tabs & other
browser functionality (or whatever will be in that top section in the future). 

I fear we're missing a big opportunity to further educate viewers of this page
on product functionality by not doing this. Remember how much traffic this page
gets!

For example on this version we could include a simple 'learn more about your
browser' link within that top module that links to /features. 

Apologies for the tardy input.
Maybe we could add a "Learn more»" link below the App Tabs header?

http://intothefuzz.com/leetom/Mozilla.com/JPG/whatsnew_06.jpg
Good idea...the placement in comment #20 seems a little too front & center though. Got any less prominent ideas?
hmmm...it doesn't look too prominent to me, especially bc it's in the hero section (don't we want them to see it?) 

To help downplay the CTA without moving it, we can try keeping "Learn more" grey, and "»" blue 

- similar to the footer links: "Release Notes >  FF Features >  FF Help >"
That could work. Mayumi?
I like the idea in Comment 22
Let's do it...Steven, what do you need from us?
(In reply to comment #25)
> Let's do it...Steven, what do you need from us?

I think I've got everything I need. I'll have to make Windows/Linux screenshots (I can do that here). will update when I have something ready for review.
(In reply to comment #3)
> Ideally we go straight from 4.0.1 to 5 however there is definitely a good
> chance that we'll have to launch a 4.0.2 between now and 5.  So there is no
> 4.0.2 planned for now but who knows.  

No 4.0.2 planned means we don't plan on doing one ;-). The only way this page will be needed if we need to do a chemspill between 4.0.1 and 5...otherwise 5 is the "point" release for 4.
First pass at this page is done in trunk in r87756. I still want to do some sanity-checking and testing on my end, but I think we're ok for review/qa:

http://www-trunk.stage.mozilla.com/en-US/firefox/4.0/whatsnew/
URL: http://www-trunk.stage.mozilla.com/en...
Keywords: qawanted
Looks like maybe a file didn't get pushed? It's appearing a bit unstyled to me...sort of a retro 1994 look.
(In reply to comment #30)
> Looks like maybe a file didn't get pushed? It's appearing a bit unstyled to
> me...sort of a retro 1994 look.

Oops, yeah. That's what happens when I commit and go to bed without looking at the page. Fixed in r87763.

Also fixed a broken image included in r87764.
Looks great, thanks!
Cleaned up styles after a successful newsletter form submit in r87818.
Merged to stage in r87874 (same merge as Bug 652017).
Status: NEW → RESOLVED
Closed: 13 years ago
Keywords: qawanted
Resolution: --- → FIXED
When does this get pushed live? 4.0.1 goes out today, so we should have this live basically now. (Right?)
I can push it if it is done...yes, if this doesn't go live today 4.0.1 users will see http://www.mozilla.com/en-US/firefox/4.0/whatsnew/
Please go ahead and push, thanks Christian. We'd like Fx4 users who get the 4.0.1 prompt to see the content on http://www-trunk.stage.mozilla.com/en-US/firefox/4.0/whatsnew/. Only thing is that the URL should be http://www.mozilla.com/en-US/firefox/4.0.1/whatsnew/ instead of 4.0.
Hmmmmm...all x.y.z whatsnew/firstrun/details pages redirect to x.y's page (I added that as I felt silly copying the same thing for every release).

I could change that for 4.0.1 but it looks like the pages above were added into the 4.0 directory.

I'm not 100% sure if a user updates from 3.5/6 to 4.0.1 if they see the whatsnew or firstrun page...
The ideal situation is that people coming from 3.5/6 see the first run page, and people coming from earlier versions of 4 see the what's new page. That's particularly relevant with the major update coming up.

But, we also want people upgrading to 4.0.1 to see the page linked above, as it ties in with a campaign Jane is running.

Very complicated, in other words! What's your recommendation?
Hmmm, I don't think that is all possible :-/. We can't determine if someone is coming from 3.5/6 or 4.0 in the update case, as the page is just given the current version (which would be 4.0.1).

I checked with rs and it looks like users going from 3.6/3.5 to 4.0.1 will get the whats new page, which is also the page used when going 4.0 to 4.0.1. The first run page is only used by people downloading 4.0.1 for the first time/without a profile.

So, sadly, it looks like we are painted into a corner and either need to have a page directed at existing 4.0 users (the page in this bug) or new 4.0 users (the current page up there). I bet you want to leave what is up there as-is.

Sorry I didn't catch this earlier and work was likely done in vain. I wasn't around for the 3.6 release and wasn't aware of this complication. Of course, once we prompt most people will already be on the new version and the case can be made for flipping to the .x focused one (the page in this bug). This is why the 3.6 page is a .x update page...we expect far less people to come from earlier versions via automatic update.
Thanks Christian. I talked it over with the other stakeholders on this page and we've decided to stick with the current flow until after the major update.

So, the work in this bug certainly wasn't done in vain but we're going to hold off from pushing it live for another couple of weeks.
Target Milestone: 2.2 → 2.4
FYI - we're still holding off on pushing this until 2.7. Opening and putting into that bucket. Thanks!
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Target Milestone: 2.4 → 2.7
Target Milestone: 2.7 → 2.6
Laura, I noticed the milestone got moved back to 2.6 on this. It's ready to go with the rest of 2.6 if that's the desired timing.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
I'm going to wait to roll this one out until I'm sure it's supposed to be. Also, I should probably talk to Steven while I'm rolling this one out. I can do it tomorrow, but marking 2.7.
Target Milestone: 2.6 → 2.7
Update here - was supposed to go out with the 2.6 milestone (since we're releasing 2.6 instead of 2.7 this week due to not releasing last week). 

This is okay to go live anytime.
pushed to production r89727
verified fixed http://www.mozilla.com/en-US/firefox/4.0/whatsnew/
Status: RESOLVED → VERIFIED
sorry to comment last minute. but reviewing the final link, we should take out the Firefox 4 beta promotion at the bottom right of the page. can we change that to promote the channel page instead? like this one: https://www.mozilla.com/en-US/firefox/5.0/firstrun/

i dont think we should promote the firefox 4 beta.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
(In reply to comment #50)
> sorry to comment last minute. but reviewing the final link, we should take
> out the Firefox 4 beta promotion at the bottom right of the page. can we
> change that to promote the channel page instead? like this one:
> https://www.mozilla.com/en-US/firefox/5.0/firstrun/
> 
> i dont think we should promote the firefox 4 beta.

Please open a new bug for that.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → 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.