Closed Bug 564020 Opened 14 years ago Closed 14 years ago

Build Firefox Cup Page

Categories

(addons.mozilla.org Graveyard :: Public Pages, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED
5.11.1

People

(Reporter: lmesa, Assigned: sgarrity)

References

()

Details

(Whiteboard: [firefoxcup])

Attachments

(5 files)

Please build the Firefox Cup campaign page. 
URL Should probably be addons.mozilla.org/firefoxcup, with firefoxcup.com redirecting to addons.mozilla.org/firefoxcup.

Will attach PSDs shortly. 
Page functionality/specs will also be attached shortly.
Assignee: nobody → steven
Attached file Page Specs
Attached file Sign Up! Email Section
This is how the email section should work. 
The copy on the Firefox Cup page should match up with what is on this doc. We'll get final PSDs on Friday and I will attach here.
Why is this an AMO bug?  All the attachments appear to be for mozilla.com.
So, the bug is hosted on AMO because the site, for Personas, needs to be on AMO.  I talked to Fligtar and he told me to file it here.
A few questions:

1. Where in AMO SVN should this page live?
2. Can I get svn commit access to wherever in AMO this should end up?
(In reply to comment #4)
> So, the bug is hosted on AMO because the site, for Personas, needs to be on
> AMO.  I talked to Fligtar and he told me to file it here.

I'm confused, can you write a project description about what you're trying to do?  We have personas linked on mozilla.com, so I don't know what you mean about needing to be on AMO for personas.  And can you attach attachments for AMO instead of mozilla.com?


(In reply to comment #5)
> A few questions:
> 
> 1. Where in AMO SVN should this page live?
> 2. Can I get svn commit access to wherever in AMO this should end up?

AMO is on github now: http://github.com/jbalogh/zamboni
Here the project plan: https://wiki.mozilla.org/WorldCup2010

Part of the page is to measure ADUs of the personas we build, so I was told the page had to be on AMO to make tracking the metrics and whitelisting easier. Also, the site is basically all about Personas and FootieFox, so it makes sense that the page would live within AMO framework.
The only URL I see is in the Campaign PDF (firefoxcup.com) and the only mention of AMO is a promotional panel on the front page.  What are the plans for AMO?

Also, what is the timeline for the project?  I see a lot of really close dates on the front page but nothing that mentions AMO.
Attached image AMO promo
(In reply to comment #8)
> The only URL I see is in the Campaign PDF (firefoxcup.com) and the only mention
> of AMO is a promotional panel on the front page.  What are the plans for AMO?

We would like the page to live on Addons.mozilla.org/FirefoxCup and for FirefoxCup.com to redirect to that page.
> 
> Also, what is the timeline for the project?  I see a lot of really close dates
> on the front page but nothing that mentions AMO.

We want the page live June 1-5th and it will run through July 20th.
We want to put a promo, taking the sports slot of the rotating home page promo on the homepage. It would fill the entire box, not just one third of it, for the duration of the tournament. 

I will file a bug once I get the promo spot which should be next week.
So, is this AMO?

> Layout Delivery 4/30/10
>     * Web Dev 5/3/10 - 5/14/10
>     * L10N 5/15/10 - 5/24/10
>     * QA 5/17/10 - 5/30/10
>     * Launch 6/1/10? 

We're a chunk into the web dev time and I haven't even seen designs yet...
(In reply to comment #11)
> So, is this AMO?
> 
> > Layout Delivery 4/30/10
> >     * Web Dev 5/3/10 - 5/14/10
> >     * L10N 5/15/10 - 5/24/10
> >     * QA 5/17/10 - 5/30/10
> >     * Launch 6/1/10? 
> 
> We're a chunk into the web dev time and I haven't even seen designs yet...

No. Steven and Alex and doing the development, AMO dev team doesnt have to do anything except help us put in the promo on the AMO homepage and help make sure the metrics work.
Hey Wil,

This is the project that Julie and I have mentioned quite a few times over the last couple months. Alex Buchanan and Steven Garrity will be doing the development so that it takes up as little AMO dev time as possible.

We want it to live on AMO because fit will involve personas, add-ons, and collections, and getpersonas.com won't be around much longer.
Justin, can I get some directly as to where this page should live? Should it live in the current AMO svn, or is the new git-based AMO stuff coming soon enough that it needs to live there? I'm assuming this will be relatively self-contained?
(In reply to comment #14)
> Justin, can I get some directly as to where this page should live?

Is this going to be a php page or a jinja template?

And can we really delete this page after July 20th?
> 
> And can we really delete this page after July 20th?

Yes. The Personas will already be hosted on AMO (since getpersonas.com is dying off) and the add-on is already hosted on AMO.
(In reply to comment #15)
> Is this going to be a php page or a jinja template?

I don't think this has been determined. It will have some basic dynamic content (importing some content from Twitter/RSS feeds), will be mostly a static/stand-alone page. Alex, do you have a preference?
Attached image Website jpg
Is there someone at AMO that can provide some guidance on where this page should end up (GIT, SVN? PHP, Python?)? I'd like to get started on implementation now.
From the uploaded image, I can't even tell what's on the page so it's hard for me to recommend anything based on that.  Both python and PHP will be around through July 20th so if you have a strong preference you're welcome to do it in whichever you'd like.  Due to the short timeline I'd suggest doing it in whichever you're most comfortable.

If you want python, you can fork http://github.com/jbalogh/zamboni and go to town.  If you want PHP, http://svn.mozilla.org/addons/trunk/site/app/ is the interesting stuff.  You can check it out from there and start working, and if you don't have commit access you can file a bug in the mean time and `svn switch` it once you do.

I'm on IRC if you have specific questions.
Depends on: 564487, 564742
Any status update here?
Requirement update:

-No longer need the column for RSS feeds.
-Email functionality should not  be a blocker.  If its easier to move ahead without the functionality, then great!
What's the status of this page?
Target Milestone: --- → 5.11
(In reply to comment #24)
> What's the status of this page?

I've got the basic HTML/CSS/image template setup as a static file here: http://github.com/sgarrity/zamboni/tree/master/firefoxcup/

It's my understanding that Alex will be taking this static page and implementing it.
I'm working on setting up Zamboni today and implementing Steven's html /css into Zamboni.
(In reply to comment #18)
> Here are the PSDs:
> 
> http://www.yousendit.com/download/OHo1ZGlobEFwM2xjR0E9PQ

This link has expired.  Could you post this somewhere on the Mozilla FTP?  And don't use expiring links in the bugs in the future please? Thanks
I'm running out the door, otherwise I'd figure out this FTP thing you speak of. 

http://www.yousendit.com/download/dXFYRkJRdWNreEJFQlE9PQ

That link should work now. I'll learn this FTP thing for next time.
Ok, got the basics set up.  Still some clean up work to do.

Repo:
git://github.com/abuchanan/zamboni.git

Latest commit:
http://github.com/abuchanan/zamboni/commit/99a6a44849bd3428793499f1df4f48b8229afa6f

Some notes:

Download button image + css missing
(do we have Firefox download button logic in Zamboni already?)
The download block title doesn't look right.

Right sidebar blocks should be links (e.g. so I can click the entire "Sign up!" block)

We shouldn't make a call to an external domain for the CSS reset sheet, e.g.
http://yui.yahooapis.com/combo?2.8.0r4/build/reset-fonts-grids/reset-fonts-grids.css
Either make this local, or in this case, I'm not sure we really need it

What's the body class javascript for?  Can we ditch that, or at least put it in a separate file and use $(document).ready ?

There was no footer in the designs.  I've included the default AMO footer, because it has the language switcher.  If you want it removed, let me know.

Steven, do you want to try and set up Zamboni, and work on the CSS from there?
(In reply to comment #29) 
> Download button image + css missing
> (do we have Firefox download button logic in Zamboni already?)

Nope.  We have enough heartache dealing with add-on buttons.
(In reply to comment #29)
> Steven, do you want to try and set up Zamboni, and work on the CSS from there?

Yeah, working on getting it setup now.
Added _() to strings.

Some notes:

Stas and I are working on how to put these strings into a separate .pot file

Steven, could you add all the countries to the table please?

How come there are height and width attributes on the Twitter <img>?

Per comment #23, I've dropped the "Latest News" column.
(In reply to comment #32)
> Steven, could you add all the countries to the table please?

Actually, nevermind.  These will be dynamically generated/ordered anyway
Rdoherty,  what needs to happen to get the Personas ADUs ?   AIUI, they will be inserted into the DB by the metrics team.  Is that already set up?  In Zamboni?
(In reply to comment #34)
> Rdoherty,  what needs to happen to get the Personas ADUs ?   AIUI, they will be
> inserted into the DB by the metrics team.  Is that already set up?  In Zamboni?

afaik, yep, they are already inserted via metrics. You'd have to talk to jbalogh about the technical details.
Laura,  to be clear, these are the hashtags i'm searching for in Twitter,
#WorldCup #Football #Soccer #South Africa2010 #Mundial

If you've added any others you want since the page specs in comment #1, please let me know (e.g. #firefoxcup ?)
(In reply to comment #36)
> Laura,  to be clear, these are the hashtags i'm searching for in Twitter,
> #WorldCup #Football #Soccer #South Africa2010 #Mundial
> 
> If you've added any others you want since the page specs in comment #1, please
> let me know (e.g. #firefoxcup ?)

How international do you want to go on this?  For instance, France terms might be:

#coupedumonde
#lacoupedumonde 
#lacoupedumondedelaFIFA
Here is a list i've pulled together, but it should be pretty international, one # per language. Seth, any ideas on how we could get the best hashtags quickly?

--#WCUP2010
--#mondial
--#mundial
--#ЧМ (russian)
--#coupedumonde (french)
--#wm  (german)
--#월드컵  (korean)
--#Wêreldbeker (Afrikaans)
--#VM (Danish)
--كأس العالم  (Arabic)
--ΠαγκόσμιοΚύπελλο  (Greek)
--#IlMondiale  (Italian)
--#W杯 (japanese)
--Светско првенство (serbian)
--Svetový pohár (slovakian)
--Svetovni pokal (slovenian)
(In reply to comment #29)
> Download button image + css missing
> (do we have Firefox download button logic in Zamboni already?)
> The download block title doesn't look right.

Since amo/zamboni doesn't have the download button infrastructure (yet?), I've reworked the entire "Get Firefox" block to be a link to mozilla.com/firefox.

> Right sidebar blocks should be links (e.g. so I can click the entire "Sign up!"
> block)
I think this might require a bit more thought. The mockup isn't entire clear on the behaviour of these blocks.

Linking the entire blocks would lead to a problem with the Firefox block, as it includes a widget (and couldn't be entirely clickable), which would make the three boxes inconsistent.

I would recommend either:
a) make an explicit text-based link in the features ("Install FootieFox Now >>", "Sign Up for Firefox Cup news by email.", etc.), or;
b) make the entire blocks clickable, but simplify the Facebook block to just be a dumb link to the Facebook page (rather than a widget).

Speaking of the Facebook widget, the mockup includes the "Become a Fan" button, which Facebook appears to have replaced with the "Like This!" (or "Recommend This") button. Should we use this (or the dumb link from (b) above)?

> We shouldn't make a call to an external domain for the CSS reset sheet, e.g.
> http://yui.yahooapis.com/combo?2.8.0r4/build/reset-fonts-grids/reset-fonts-grids.css
I've made this local.

> What's the body class javascript for?  Can we ditch that, or at least put it in
> a separate file and use $(document).ready ?
This javascript is for the random featuring of add-ons in the sidebar. The script randomly adds a CSS class to the body, which is used to show/hide a particular sidebar feature. I could go into a separate JS file, but that would be one more http-request - this works.
 
> There was no footer in the designs.  I've included the default AMO footer,
> because it has the language switcher.  If you want it removed, let me know.
I see there is a mockup in Basecamp now with a language switcher in the header. Should we re-work the page to follow this mockup (Alex, can this even be done?), or should we keep the AMO footer, which brings a long a language switcher already?

> Steven, do you want to try and set up Zamboni, and work on the CSS from there?
Done. I'm still figuring out the general git (and github) workflow. I've been making changes in http://github.com/sgarrity/zamboni - should I just use GitHub pull requests when I have changes?

Laura, can you weigh in on the points/questions I've brought up here? Thanks.
(In reply to comment #39)
> (In reply to comment #29)
> > Download button image + css missing
> > (do we have Firefox download button logic in Zamboni already?)
> > The download block title doesn't look right.
> 
> Since amo/zamboni doesn't have the download button infrastructure (yet?), I've
> reworked the entire "Get Firefox" block to be a link to mozilla.com/firefox.
> 
> > Right sidebar blocks should be links (e.g. so I can click the entire "Sign up!"
> > block)
> I think this might require a bit more thought. The mockup isn't entire clear on
> the behaviour of these blocks.
> 
> Linking the entire blocks would lead to a problem with the Firefox block, as it
> includes a widget (and couldn't be entirely clickable), which would make the
> three boxes inconsistent.
> 
> I would recommend either:
> a) make an explicit text-based link in the features ("Install FootieFox Now
> >>", "Sign Up for Firefox Cup news by email.", etc.), or;
> b) make the entire blocks clickable, but simplify the Facebook block to just be
> a dumb link to the Facebook page (rather than a widget).

I vote for this option. 
> 
> Speaking of the Facebook widget, the mockup includes the "Become a Fan" button,
> which Facebook appears to have replaced with the "Like This!" (or "Recommend
> This") button. Should we use this (or the dumb link from (b) above)?

Let's use the dumb link from B.  We are having internal disagreements about whether to host the FB "Like" button on any of our sites, so I want to steer clear of the issue if we can. 
> 
> > We shouldn't make a call to an external domain for the CSS reset sheet, e.g.
> > http://yui.yahooapis.com/combo?2.8.0r4/build/reset-fonts-grids/reset-fonts-grids.css
> I've made this local.
> 
> > What's the body class javascript for?  Can we ditch that, or at least put it in
> > a separate file and use $(document).ready ?
> This javascript is for the random featuring of add-ons in the sidebar. The
> script randomly adds a CSS class to the body, which is used to show/hide a
> particular sidebar feature. I could go into a separate JS file, but that would
> be one more http-request - this works.
> 
> > There was no footer in the designs.  I've included the default AMO footer,
> > because it has the language switcher.  If you want it removed, let me know.
> I see there is a mockup in Basecamp now with a language switcher in the header.
> Should we re-work the page to follow this mockup (Alex, can this even be
> done?), or should we keep the AMO footer, which brings a long a language
> switcher already?

I like the language switcher that NoBox sent over, but do whatever is easier. 
> 
> > Steven, do you want to try and set up Zamboni, and work on the CSS from there?
> Done. I'm still figuring out the general git (and github) workflow. I've been
> making changes in http://github.com/sgarrity/zamboni - should I just use GitHub
> pull requests when I have changes?
> 
> Laura, can you weigh in on the points/questions I've brought up here? Thanks.
Laura, Ryan,

I see there is a Total Fans column in the table, but afaik the only count we keep is ADU (i.e. Average Fans).  Is there a total count that I'm missing, or shall I drop this column?
(In reply to comment #41)
> Laura, Ryan,
> 
> I see there is a Total Fans column in the table, but afaik the only count we
> keep is ADU (i.e. Average Fans).  Is there a total count that I'm missing, or
> shall I drop this column?

Drop it imo, we only track ADUs.
(In reply to comment #41)
> Laura, Ryan,
> 
> I see there is a Total Fans column in the table, but afaik the only count we
> keep is ADU (i.e. Average Fans).  Is there a total count that I'm missing, or
> shall I drop this column?

Oh, sorry, I see this now in the Page Specs attachment,

Average is calculated from the day the site goes live and is total number of ADUs divided by the number of days the site has been live.
Total fans are the total # of ADUs
Hehe, yep that's right. 

Thanks!
(In reply to comment #43)

> Average is calculated from the day the site goes live and is total number of
> ADUs divided by the number of days the site has been live.
> Total fans are the total # of ADUs

In that case, shouldn't "Total" be renamed to "Today"? (ADU is "daily", correct?)
(In reply to comment #45)
> (In reply to comment #43)
> 
> > Average is calculated from the day the site goes live and is total number of
> > ADUs divided by the number of days the site has been live.
> > Total fans are the total # of ADUs
> 
> In that case, shouldn't "Total" be renamed to "Today"? (ADU is "daily",
> correct?)

Makes sense to me
The Page Specs say there should be a rotating promo between Footie Fox, RYFX, and AMO.  Those promos haven't been implemented yet, and weren't part of the design afaik.  

Do we still need them?  If yes, where are the designs for those promos?
(In reply to comment #47)
> The Page Specs say there should be a rotating promo between Footie Fox, RYFX,
> and AMO.  Those promos haven't been implemented yet, and weren't part of the
> design afaik.  
> 
> Do we still need them?  If yes, where are the designs for those promos?

I was thinking of using the ones we already have running on the What's New Page.  I asked NoBox to make the promo box the same size as those promos, but if they aren't the same size, then I don't think its worth time stressing about it.  We can set the page up without the rotating promos.  

Julie, how hard would it be to get those two promos, RYF and AMO resized (if needed)?
I've got simplified versions of the RYF/AMO promos in the style of the FootieFox promo from the mockup implemented.

Also, what level of support do we need for IE on this page? Currently, it looks bad (but is readable) in IE6, and looks ok in IE7/8, but the boxes are missing rounded corners and some borders/gradients.
(In reply to comment #49)
> I've got simplified versions of the RYF/AMO promos in the style of the
> FootieFox promo from the mockup implemented.
> 
> Also, what level of support do we need for IE on this page? Currently, it looks
> bad (but is readable) in IE6, and looks ok in IE7/8, but the boxes are missing
> rounded corners and some borders/gradients.

I wouldn't worry about IE6--but IE7 and 8 are important.
Laura, can you take a look at comment 45, please?
(In reply to comment #45)
> (In reply to comment #43)
> 
> > Average is calculated from the day the site goes live and is total number of
> > ADUs divided by the number of days the site has been live.
> > Total fans are the total # of ADUs
> 
> In that case, shouldn't "Total" be renamed to "Today"? (ADU is "daily",
> correct?)

Sorry!  Yes, we can call it "Today".
Depends on: 567533
Depends on: firefoxcup-l10n
Depends on: 565754
Page should show up here soon:
https://preview.addons.mozilla.org/z/en-US/firefoxcup/
(which is currently broken from bug 568317)

Still a couple things missing, including Average Fans, geolocation (sgarrity could you provide an update?), and possibly the Personas are not yet synced (see bug 568026)
We've been looking into using HTML5 geolocation to default the preview image to the nearest team. While we can easily get a latitude/longitude location, translating that to a country (or nearest country) appears to be a relatively difficult.

Possible options include: 

a) Setting up our own local database of country co-ordinates based on this system: http://wiki.openstreetmap.org/wiki/Nominatim#Reverse_Geocoding_.2F_Address_lookup

b) Use the Google Maps web service for reverse geocoding to get the country from lat/long: http://code.google.com/apis/maps/documentation/geocoding/#ReverseGeocoding - however, there is a rate-limit of 2,500 requests per day (with a commercial option of paying for up to 10,000 for pay)
CSS fixes, and average fans should be on preview.amo soon

commit:
http://github.com/abuchanan/zamboni/commit/0fc810538c4ae276f3d0f3f92e098a746364c7e7
As a guy that clicked on the promo and then installed a persona, "Average Fans" and "Fans Today" mean nothing to me.  What do those mean?  Average I have no idea about, "Fans Today" sounds like people who just signed up today.

All I care about is, "Is my team winning right now?"  If you want to show some kind of average or history a sparkline makes more sense (see http://www.mozilla.com/en-US/firefox/stats/ after it comes back up for an example).
(In reply to comment #56)
> As a guy that clicked on the promo and then installed a persona, "Average Fans"
> and "Fans Today" mean nothing to me.  What do those mean?  Average I have no
> idea about, "Fans Today" sounds like people who just signed up today.
> 
> All I care about is, "Is my team winning right now?"  If you want to show some
> kind of average or history a sparkline makes more sense (see
> http://www.mozilla.com/en-US/firefox/stats/ after it comes back up for an
> example).

Good point.  I like it.  Laura / Mary, thoughts? 

So the sparkline data points would be each day's ADU count, right?  Teams would be placed by today's ADU count (currently teams would be placed by the average fans metric)

Also, this would mean a string change, and Stas already requested 'no more strings changes' this morning.  Stas, what do you think?
What would the new copy be?
(In reply to comment #58)
> What would the new copy be?

I'm thinking just one column with "Fans" as a heading.  Clouserw?
Perfect
(In reply to comment #59)
> (In reply to comment #58)
> > What would the new copy be?
> 
> I'm thinking just one column with "Fans" as a heading.  Clouserw?

I'm good with that too.
What is the status of this?
The last thing I'm working on is randomly switching displaying a team persona preview sample image. Should be ready today. Alex may have other status to report.
Todo:

* new languages, bug 567533
* Add-ons misspelled, bug 569037
* Average/Total Fans -> Fans + sparkline
* implement personas install on click
* hide "Get Firefox" promo for 3.6 users
* always show FootieFox promo
* page validation, bug 568866
(In reply to comment #64)
> Todo:
> 
> * new languages, bug 567533
> * Add-ons misspelled, bug 569037
> * Average/Total Fans -> Fans + sparkline
> * implement personas install on click
> * hide "Get Firefox" promo for 3.6 users
> * always show FootieFox promo
> * page validation, bug 568866

What is critical before going live and what is the ETA?
Depends on: 568900
Depends on: 568594
Depends on: 569374
(In reply to comment #64)

> * Add-ons misspelled, bug 569037

This has an l10n impact, I'm working with Alex on fixing this without breaking the locales.

> * Average/Total Fans -> Fans + sparkline

We still don't have the translation of "Fans". We only have "Fans Today", "Total Fans" and "Average Fans". I'd prefer to ask localizers to provide the new translation once we have the sparklines in place, so that they can choose the best wording. Alex, any ETA on this particular todo on your list?

> * always show FootieFox promo

Related to this, I filed bug 569374 reported by a localizer.
One more thing: we're generally pretty close to 100% for localization and we were able to do some l10n testing on the staging server. But, it would be hugely helpful to have a silent launch on the production AMO ca. 3 days before the real launch is supposed to happen. Not sure if we can cram these additional 3 days into the schedule at this point, but I thought I'd mention this anyways. Thanks.
These are fixed locally (not yet committed to master / preview.amo)

* hide "Get Firefox" promo for 3.6 users
* always show FootieFox promo
* page validation, bug 568866
* new languages, bug 567533


Stas is working on this one:

* Add-ons misspelled, bug 569037


I'm working on these, should be done in a couple hours.

* Average/Total Fans -> Fans + sparkline
* implement personas install on click

 
> What is critical before going live and what is the ETA?

It should all get fixed.  I'm aiming to have all this committed this afternoon.


> > * Average/Total Fans -> Fans + sparkline
> 
> We still don't have the translation of "Fans". We only have "Fans Today",
> "Total Fans" and "Average Fans". I'd prefer to ask localizers to provide the
> new translation once we have the sparklines in place, so that they can choose
> the best wording. Alex, any ETA on this particular todo on your list?

Working on it now, should be on preview.amo this afternoon
 
> > * always show FootieFox promo
> 
> Related to this, I filed bug 569374 reported by a localizer.

Fixed.
Ok, done coding to TODO list, working on merging in sgarrity's changes, getting review, and merging all that to master
(In reply to comment #69)
> Ok, done coding to TODO list, working on merging in sgarrity's changes, getting
> review, and merging all that to master

merged to master
http://github.com/jbalogh/zamboni/commit/4462f121a248671fca4669602fdd93623223a8f0
The sparklines are flat because the stats cronjobs haven't run yet.  This looks weird since there are non-zero numbers next to them.  I'll fix that.
Page is looking really nice!  One thing I haven't seen is the default persona NoBox sent over.  I don't think its a blocker by any means, but it would be cool to have that Persona in the mix too. Mary, do you think its worth trying to get in in the page?
O, yikes - I didn't upload that one.  Will do that now.  Looks like we'll need to either have 4 "pages" of Personas (with 9 on the last) or 5 pages since it will jump to 33.  

Uploading now.
This was supposed to have been frozen a week ago and our push is tomorrow.  We can't keep editing this page.  Please file a separate bug to add the new persona.

As far as this bug, please tell me if there is anything else blocking this push right now and what the ETA is.  The next push after tomorrow is in a couple weeks - maybe that's a better timeline for this project.
Will do -- it was actually not sent over. We need to keep the launch at June 10th and will try to wrap up everything today.
Thanks!
No longer depends on: 564487, 564742
Target Milestone: 5.11 → 5.11.1
(In reply to comment #73)
> O, yikes - I didn't upload that one.  Will do that now.  Looks like we'll need
> to either have 4 "pages" of Personas (with 9 on the last) or 5 pages since it
> will jump to 33.  

Not sure if we're going to make this change now (Alex?), but fwiw, adding a 5th slide should be safe l10n-wise.
Just a small note, there isn't any way for users to share/link/tweet/etc this page. Maybe it can be added at a later date? AMO has a localized sharing widget that can possibly be re-used (under thumbnail on this page https://addons.mozilla.org/en-US/firefox/addon/10548/).
It would be awesome to add it - will file a separate bug aiming for release next Tuesday.
Can we close this?
Yep, we have separate bugs for everything left.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Whiteboard: [firefoxcup]
verified fixed on https://preview.addons.mozilla.org/z/en-US/firefoxcup/
Status: RESOLVED → VERIFIED
Blocks: 571231
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: