Closed
Bug 562686
Opened 15 years ago
Closed 15 years ago
Apply new firstrun page design to whatsnew page
Categories
(www.mozilla.org :: General, defect)
www.mozilla.org
General
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: sgarrity, Assigned: sgarrity)
References
()
Details
There's a fan-C-pants new design being implemented on the firstrun page in Bug 555098. This bug will track the application of this design to the whatsnew page.
Assignee | ||
Comment 1•15 years ago
|
||
While the firstrun page is exists only once for the major version # (3.6), a new copy of the whatsnew page is created for each release. We've got:
/en-US/firefox/3.6/whatsnew/
/en-US/firefox/3.6.2/whatsnew/
/en-US/firefox/3.6.2rc/whatsnew/
/en-US/firefox/3.6.3/whatsnew/
/en-US/firefox/3.6.3plugin1/whatsnew/
/en-US/firefox/3.6.4rc/whatsnew/
Should we update all of the 3.6.* whatsnew pages, or just the first (3.6 proper) and most recent?
Comment 2•15 years ago
|
||
Perhaps we should wait to see whether the new design performs better than the existing design before implementing it on both the First Run and What's New pages.
Comment 3•15 years ago
|
||
(In reply to comment #2)
> Perhaps we should wait to see whether the new design performs better than the
> existing design before implementing it on both the First Run and What's New
> pages.
Why not implement the new design and test it against the existing one? Seems like we could learn a lot that way.
Assignee | ||
Comment 4•15 years ago
|
||
If it makes a difference in the decision, the whatsnew pages share a lot of resources with the firstrun page, so applying the new design to the whatsnew pages will not be a major project.
Comment 5•15 years ago
|
||
Okay, in that case it doesn't matter. Just thought I'd try to save you some work.
Assignee | ||
Comment 6•15 years ago
|
||
Could I get a final decision on which versions of the whatsnew page should get this treatment? (see comment #1).
Comment 7•15 years ago
|
||
I say we implement the design on 3.6.4rc and beyond.
This would just be for final releases, correct?
The rc's have the beta/robot look:
http://www.mozilla.com/en-US/firefox/3.6.2rc/whatsnew/
And the finals have the look this bug wants to revamp:
http://www.mozilla.com/en-US/firefox/3.6.2/whatsnew/
Also, for final releases the content doesn't change. I'm planning on redirecting any final build's whatsnew to the general one for the release (3.6.4/whatsnew -> 3.6/whatsnew, 3.6.4rc/whatsnew no redirect). There are similar ones in place for firstrun already (http://viewvc.svn.mozilla.org/vc/projects/mozilla.com/tags/production/.htaccess?view=markup#l177).
Comment 9•15 years ago
|
||
Christian is right. 3.6.4 version release and every final version after that.
Assignee | ||
Comment 10•15 years ago
|
||
Done in trunk in r67006 to en-US/firefox/3.6/whatsnew/
Updated•15 years ago
|
Comment 11•15 years ago
|
||
I know I'm late to the party, but we should be using our CDN as much as possible (see bug 545548); this is something that probably shouldn't block this page, but should be done eventually.
Comment 13•15 years ago
|
||
Please add the add-on src parameters and links mentioned in the firstrun page bug (bug 555098) to this page as well, except change the src from fxfirstrun to fxwhatsnew.
Thanks!
Assignee | ||
Comment 14•15 years ago
|
||
The featured add-ons, src parameters, and wording have been updated here on the whatsnew page to match the firstrun page updates from Bug 555098.
Assignee | ||
Comment 15•15 years ago
|
||
Use CDN for scripts in header and new jquery-based input-placeholder script in r67242.
(In reply to comment #15)
> Use CDN for scripts in header and new jquery-based input-placeholder script in
> r67242.
What about the static images (Firefox logo, other non-Personas graphics); can you do those too?
Assignee | ||
Comment 17•15 years ago
|
||
(In reply to comment #16)
> What about the static images (Firefox logo, other non-Personas graphics); can
> you do those too?
They were done as well. The image now either have the static-prefix or are embedded directly in the CSS with the data URI scheme.
Assignee | ||
Comment 18•15 years ago
|
||
A few more images using the static-prefix in r67292.
I've taken another look at both this page and the First Run page over in bug
562686, and it looks good (validated doctype, checked links, Persona hovers,
etc.)
Assignee | ||
Comment 20•15 years ago
|
||
Merged to stage in r67318.
https://www.authstage.mozilla.com/en-US/firefox/3.6/whatsnew/
Assignee | ||
Updated•15 years ago
|
Keywords: push-needed
Comment 21•15 years ago
|
||
Thanks Steven. Are the files in r67318 the only ones I need to push live?
Assignee | ||
Comment 22•15 years ago
|
||
(In reply to comment #21)
> Thanks Steven. Are the files in r67318 the only ones I need to push live?
Yes, that's it.
Comment 23•15 years ago
|
||
Pushed the files - should be live soon. Thanks all!
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Verified FIXED; John, when you push live, please remove "push-needed" from the keyword field; thanks!
Status: RESOLVED → VERIFIED
Keywords: push-needed
Updated•13 years ago
|
Component: www.mozilla.org/firefox → www.mozilla.org
Updated•13 years ago
|
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.
Description
•