Closed Bug 1085504 Opened 11 years ago Closed 11 years ago

[Firefox 10th] MDN Banner Update (copy)

Categories

(Marketing :: Copy, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
Due Date:

People

(Reporter: lizzn, Assigned: tpalmer, Mentored)

References

(Blocks 1 open bug)

Details

>>Project/Request Title: [Firefox 10th] MDN Banner Update (copy) >>Project Overview: We met with the MDN earlier this week to scope out a ad-like campaign on MDN. Something that hasn't been done before but they see the value in promoting Dev Edition to their audience. Think of these as content ads focused on generating awareness to a developer audience. I took a stab at the messaging and sharing FWIW: "Build the web with Firefox Developer Edition. The only browser designed for developers like you. Learn more." That being said, this is the ask: see slide 15 of this deck: https://docs.google.com/a/mozilla.com/presentation/d/11Nvz2KQkOANQehKaiuYteP_-9xyqb7g859rLX_f6hTk/edit#slide=id.g4306d026b_023 >> Creative Help Needed: Copy: Yes Design: No Video: No Other: No >>Creative Specs: 1. Top page banner: logo and copy only 2. Front page tile ad: Logo on one-color background and copy - Dimensions: 432px x 168px 3. Tile ad: Logo on one-color background and copy - Dimensions: 250 px x 169 px 4. Developer Edition Intro on Dev Tools (replacing Aurora copy): https://developer.mozilla.org/en-US/docs/Tools Copy only. This can be pulled from product page copy deck. >>CTA and Design: See above. >>Creative Due Date: 2014-10-31 >>Launch Date: 2014-11-10 >>Mozilla Goal: Firefox OS >>Points of Contact: alainez@mozilla.com, epetitt@mozilla.com, Mnovak@Mozilla.com
Blocks: 1085493
Blocks: 1079423
No longer blocks: 1085493
Blocks: 1085493
Assignee: Mnovak → troy
Status: NEW → ASSIGNED
Due Date: 2014-10-31
Is there a rough copy outline / expectation for the Intro paragraph (item no. 4 in the specs listed above)? The Aurora copy has six bullet points / links and I'm just wondering if I should be looking at doing something similar for the Dev Edition, or if I should just provide more of a standard paragraph. Thanks, Troy
Hey everyone Here is the link to copy deck — it contains copy for the MDN banner and copy for an intro on Developer Tools MDN page. https://docs.google.com/document/d/1VHuQCO3TeEnWhUuticlMPWaRtj4hVqt0Zpy9qF8LK8g/edit?usp=sharing Please let me know if there are any questions. Thanks, Troy
Hi all, Please take a look at these banners and let me know if I'm missing anything: http://cl.ly/1h0E2H043F0z
Hey Lee (and everyone) After seeing the layouts with the full logo in place, I'm thinking we can probably take the name out of the copy line (just like we did with the product page headline). If it fits, I'd suggest we go with something like this for all of the different sizes: LOGO - Firefox Developer Edition COPY - Build the Web with the only browser built for developers. Thoughts?
What if it were something like this? LOGO - Firefox Developer Edition COPY - Introducing our first ever browser built for those who build the Web.
That works for me. Thanks. (In reply to Matej Novak [:matej] from comment #5) > What if it were something like this? > > LOGO - Firefox Developer Edition > COPY - Introducing our first ever browser built for those who build the Web.
Thanks for the quick revisions, guys. Here are the updated assets: http://cl.ly/0P253Z021O1e
(In reply to Lee Tom from comment #7) > Thanks for the quick revisions, guys. > > Here are the updated assets: http://cl.ly/0P253Z021O1e Hey Lee, that link gives me the same layouts as before.
Oopps! Cloud app'd the wrong .zip folder - http://cl.ly/0c2g3u0u1K06 (In reply to Matej Novak [:matej] from comment #8) > (In reply to Lee Tom from comment #7) > > Thanks for the quick revisions, guys. > > > > Here are the updated assets: http://cl.ly/0P253Z021O1e > > Hey Lee, that link gives me the same layouts as before.
(In reply to Lee Tom from comment #9) > Oopps! > Cloud app'd the wrong .zip folder - http://cl.ly/0c2g3u0u1K06 The two smaller ones still repeat the name of the product. I know there are space limitations there, but maybe they could be: Built for those who build the Web Would that fit?
can you guys make changes to the copy doc and let me know when you think it's final. I can't make new assets for every iteration.
(In reply to Lee Tom from comment #11) > can you guys make changes to the copy doc and let me know when you think > it's final. I can't make new assets for every iteration. I'm on PTO today, so I'll let you and Troy sort it out, but the suggestions in comment 4 and comment 5 were supposed to be for all sizes, so this isn't a new iteration.
I'll update the doc and post here when it's done. Stay tuned.
That wasn't clear as 2 of the assets had copy plus CTAs. The other 2 just had CTAs. (In reply to Matej Novak [:matej] from comment #12) > (In reply to Lee Tom from comment #11) > > can you guys make changes to the copy doc and let me know when you think > > it's final. I can't make new assets for every iteration. > > I'm on PTO today, so I'll let you and Troy sort it out, but the suggestions > in comment 4 and comment 5 were supposed to be for all sizes, so this isn't > a new iteration.
Hey Lee Sorry for the confusion. We did have a "learn more" CTA on there that it looks like we're taking that out now — I don't think it's needed on the banners and tiles. I've updated the copy doc with lines for each of the sizes you've been working to. There's also a copy line in there for a banner that is to appear at the top of MDN page, but I think that's copy only (see the Project Overview in the first comment). If I'm wrong on that though, please let me know. https://docs.google.com/document/d/1VHuQCO3TeEnWhUuticlMPWaRtj4hVqt0Zpy9qF8LK8g/edit?usp=sharing Thanks, Troy
THanks for updating the copy doc (with obsolete copy strike-throughs) and listing the assets, Troy. It's really helpful seeing like that. Here's the new batch of assets: http://cl.ly/1e3m3f2K2H2Z
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.