Closed Bug 735411 Opened 13 years ago Closed 11 years ago

[3.6 EOL/Start Page Migration] Implement new start page

Categories

(Websites :: Firefox Start, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: lforrest, Assigned: jpetto)

References

Details

See wiki page here for info: https://wiki.mozilla.org/Engagement/Product_Marketing/3.6_Upgrade/StartPage Timing: With 3.6 EOL project which falls on the Fx12 launch 4/24
Assigning this bug to Christie as she is going to lead this project.
Assignee: chrismore.bugzilla → ckoehler
My initial thoughts from an l10n perspective (dumping my brain ;) : 1/ Will this page be on www.mozilla.org or will a new mini-site be built for this migration ? 2/ The wiki page says: "keep main search functionality and general design of the current about:home page" -> Do you know if google.com/firefox had per locale specific search parameters or can we put the same search parameters for all locales? (CCed Pike in case he knows, but that's probably a question Google could answer better). 3/ The page must work with rtl languages (general design, graphics...) 4/ We have almost all locales we had for 3.6 supported on mozilla.org and we also host the translations of the snippets we use for the snippets service there, it would probably makes things simpler (from an l10n POV ;) ) to have this page hosted there. 5/ We probably have special cases we need to deal with that require specific messaging, for example we lost the Occitan locale with 3.6, given that Occitan is a regional language in France I would prefer that we put a message in French on this page instead of English and take this oportunity to propose them to help getting current Firefox in Occitan. For some other locales, we may want to propose them to either use a final release in English or a beta version in their language. 6/ Wherever it is hosted, we need to be able to have per-locale css fixes to make the page look good for all locales.
PS: The current URL that people have is http://__AB_CD__.start3.mozilla.com/firefox, with __AB_CD__ being the locale code. I guess the most performant way to do this would be to host a mini-site that CNAMEs to those. Regarding "current" behaviour, I'm unsure if "current" refers to currently-3.6 or currently in-product about:home. Mostly impacts what we want to do with snippets and how.
Design complete, see bug 734197.
OS: Mac OS X → All
Hardware: x86 → All
Assignee: ckoehler → jon
Depends on: 742564
Depends on: 742648
Depends on: 743248
Some Firefox 4+ users have set the old Start Page (www.google.com/firefox) as their homepage in certain circumstances. I have seen many tweets claiming "The Start Page says: You're not on the latest version of Firefox. My Firefox is up-to-date!" That means the static copy on the Start Page is inappropriate. Do you have a plan to implement some kind of version check on the Start Page? If you've discussed that, please discard my comment.
Kohei: That's a good point, thanks (though it should be a separate bug).
Depends on: 744055
Component: Other → Firefox Start
QA Contact: other → firefox-start
Couple of changes from Ty regarding the current implementation: * Reduce the vertical space between "Your Browser..." and "Upgrade today for the latest in speed and security." * New image for alert graphic, Ty will provide * Overlay should line up with left an right edges of search box (should be exactly same width) * Ty will work with Jon to make better background gradient
Commit pushed to master at https://github.com/mozilla/fx36start https://github.com/mozilla/fx36start/commit/2ad114aa90cbd0eed1ddd4aa47222d8a45437f45 updated width/positioning of modal to match search box below, only showing modal for version 3.6.x, added alt text to 'No thanks...' link, reduced space after 'Your browser...' headline. bug 735411
Depends on: 745949
Depends on: 745951
Ty, the changes look good to me. Will you verify?
Depends on: 744848
Depends on: 743831
Closing as all dependencies have been resolved.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.