[One Mozilla] Pull /firefox site edge cases

RESOLVED FIXED in 1.11

Status

RESOLVED FIXED
7 years ago
6 years ago

People

(Reporter: christine.brodigan, Assigned: sgarrity)

Tracking

unspecified
1.11
x86
Mac OS X

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

7 years ago
Steven & James let's use this bug to pull edge cases from pages like the video page on the current /firefox site that have hidden complexity.

Laura and I will circle back with the product owners to figure out future plans for these pages and if they should be migrated to Bedrock or if we can create an alternate plan for something simpler and more effective.
(Assignee)

Comment 1

7 years ago
http://mozilla.org/firefox/video/
A dynamic page with an array of videos. URL vars swap out the default video (eg. http://www.mozilla.org/en-US/firefox/video/?video=awesome)

http://mozilla.org/firefox/channel/ & http://mozilla.org/firefox/aurora/
Includes an RSS feel pulled in from a WordPress blog via PHP and a newsletter signup form.

http://mozilla.org/en-US/press/
Pulls in content from a WordPress blog - may be replaced or significantly updated in Bug 697511?

http://mozilla.org/firefox/X.X/whatsnew/
The whatsnew pages include some simple but dated/obscure checks to see what version you're running and display different messages accordingly. Should be updated.
This is a good discussion to have, but we don't have to technically cover 100% of the edge cases here. We can migrate page-per-page and make sure we cover all the edge cases for that specific page. Also, there's a bunch of edge cases that I'm sure we'll only uncover while trying to port the code, fwiw.

Discussing in general the spectrum of edge cases is great though, with an effort to simplify the site into something consistent.
Most of the weird edges for our main pages are probably in the prefetch file:

http://viewvc.svn.mozilla.org/vc/projects/mozilla.com/trunk/includes/prefetch.php?revision=97502&view=markup

I bet that can simplified in the process of porting the site.

Also, we have a ton of weird redirects but those don't have to change. We will run the Apache .htaccess file in front of bedrock just like we do with our current site.

Updated

7 years ago
Target Milestone: 4.8 → 4.9

Updated

7 years ago
Target Milestone: 4.9 → 4.10
(Reporter)

Updated

7 years ago
Target Milestone: 4.10 → 4.12

Updated

7 years ago
Target Milestone: 4.12 → 1.0

Updated

7 years ago
Target Milestone: 1.0 → 1.1

Updated

7 years ago
Target Milestone: 1.1 → 1.2

Updated

7 years ago
Target Milestone: 1.2 → 1.3

Updated

7 years ago
Target Milestone: 1.3 → 1.4

Updated

7 years ago
Target Milestone: 1.4 → 1.5

Updated

7 years ago
Target Milestone: 1.5 → Future
(Reporter)

Comment 4

7 years ago
Steven,

Can you pull the edge cases from the /firefox site that we need to have Lee do more design polish in PSDs for migration to Bedrock

(e.g. /new. /fx ?)

Here's the final content inventory for en-US (first tab) for desktop, second tab for mobile (NOT /m that's staying put).

https://docs.google.com/spreadsheet/ccc?key=0AlGDfFgIIbD9dDJOYjRydFJENXk5ZUgxQ2Z6Uk9OT1E#gid=0
Target Milestone: Future → 1.11

Comment 5

7 years ago
Just checking back in on this, b/c I'd like to have Lee get started next week. 

Sounds like we don't have to or won't be able to cover ALL the edge cases here, but what are the main ones? Off the top of my head I'm thinking of /firefox, /new, /whatsnew (if that's even still applicable...maybe not), /firstrun...any others?
(Assignee)

Comment 6

7 years ago
/firefox and /new are definite candidates for design review. The recent /firstrun and /whatsnew pages could stand an update too - but we could leave those looking exactly as they do now (since they didn't really match the old site either) if necessary.

Would be nice to have Lee take a look at at least one page with the dark aurora style. Probably /firefox/aurora/ (which I'm noticing now has the background alignment broken...).
(Reporter)

Comment 7

7 years ago
OK, here's my vote for the list of pages we need Lee's help with, criteria = lots of screen captures/images that need to be adjusted to the new background & pages with background images:

http://www.mozilla.com/en-US/firefox/new/
http://www.mozilla.com/en-US/firefox/fx
http://www.mozilla.org/en-US/firefox/central/
http://www.mozilla.org/en-US/firefox/10.0/firstrun/index.html (FX11)
http://www.mozilla.org/en-US/firefox/10.0/whatsnew/index.html (FX11)
http://www.mozilla.org/en-US/firefox/aurora/
http://www.mozilla.org/en-US/firefox/features/(because so many images will need to be edited to work with the new background)
http://www.mozilla.org/en-US/mobile/features/ (same as above - tons of screen captures)
http://www.mozilla.org/en-US/firefox/beta/
http://nightly.mozilla.org/

John, should I open up a design bug with this list?

Comment 8

7 years ago
Yes, please do open a design bug with that list. Be sure to mention the due date(s) as well.

Thanks!
(Reporter)

Comment 9

7 years ago
Bug 733828 opened and assigned to Lee

Due date for all of these pages to be live is March 29, 2012, but none are a blocker to any other, so they can be tackled on a rolling basis.

Steven if you can sync with Lee that would be AMAZING. Let me know how I can be more helpful in this process.
(Assignee)

Updated

7 years ago
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Component: www.mozilla.org/firefox → www.mozilla.org
Product: Websites → Websites
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.