Closed Bug 401035 Opened 14 years ago Closed 14 years ago
Implement extend Firefox contest banner ads on AMO pages
Attaching two images for banner ads. Landing page should be http://labs.mozilla.com/contests/extendfirefox/ We should run these on: - front page - category pages (e.g. https://addons.mozilla.org/en-US/firefox/browse/type:1/cat:1) - browser by category (https://addons.mozilla.org/en-US/firefox/browse/type:1) Not on: - individual add-on details pages - recommended list page - search results page
OS: Mac OS X → All
Hardware: PC → All
Target Milestone: --- → 3.1
If possible, let's use the following url's for each of these (2) banners: 468x60: http://labs.mozilla.com/contests/extendfirefox/?utm_source=amo&utm_medium=banner&utm_content=468x60&utm_campaign=0710extendffxcontest 728x90: http://labs.mozilla.com/contests/extendfirefox/?utm_source=amo&utm_medium=banner&utm_content=728x90&utm_campaign=0710extendffxcontest
Soft ping to morgamic, wil and fligtar - any ideas about how we can get this out soon?
Assignee: nobody → morgamic
Seriously, though, we should put up the contest form before throwing up the banner ad. I can do this. The contest form itself will hopefully be up by Nov. 1 but it's going to be interesting since I only heard about it this morning at 9am.
We should probably only show these if the user is browsing in en-US. Since they're only in English. And stuff.
(In reply to comment #6) > Seriously, though, we should put up the contest form before throwing up the > banner ad. I can do this. > > The contest form itself will hopefully be up by Nov. 1 but it's going to be > interesting since I only heard about it this morning at 9am. > You don't need to fill out the form to get started, only to submit your final entry. The deadline is going to be December 31st at midnight. We've launched the promotional campaign already and the site is live. No dependency on getting the banners on AMO.
What is the status for getting these banners on AMO? Can I provide any additional info? Just let me know, thanks! Rhian
Did want to ask which page should house which size banner? Any info on that?
Here is my suggestion, let's use only the 468x60 for now...the other seems too large for the design of the site. Front page (https://addons.mozilla.org/en-US/firefox/) Category pages (e.g. https://addons.mozilla.org/en-US/firefox/browse/type:1/cat:1) Browser by category (https://addons.mozilla.org/en-US/firefox/browse/type:1) Also, I think we might have a problem with two Firefox logos appearing but let's see what it looks like.
Didn't have to use the small one, so please direct if I am not placing where it should be.
Comment on attachment 287137 [details] [diff] [review] v2, using smaller image as requested r=fligtar on code... as far as ui-r, the banner doesn't really go with the site at all and makes everything look pretty ugly. And we're not displaying it in the Developer Control panel, the one part of the site that is for developers.
Attachment #287137 - Flags: review?(fligtar) → review+
I put the wrong dimensions in the original banner href, but fixed that (talking about the <a href=" link to the page drolo requested).
Can I please get some feedback on this banner?
Looks fine to me.
(In reply to comment #19) > Can I please get some feedback on this banner? > I agree with comment #16. The banner doesn't really go with the site's theme at all and looks really out of place.
I agree with Basil, it looks fine and we need to get this info out to AMO site visitors.
(In reply to comment #22) > I agree with Basil, it looks fine and we need to get this info out to AMO site > visitors. > i agree, except s/site visitors/developers/ -- primary audience and target are add-ons developers. once we have winners, then a general audience promo would make sense.
Can we post this banner today? Let me know if you need additional info. thanks! Rhian
Yes, we will.
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.