Closed
Bug 1102425
Opened 10 years ago
Closed 10 years ago
Firefox OS Hungary launch email
Categories
(Marketing :: Design, task)
Tracking
(Not tracked)
RESOLVED
FIXED
Due Date:
People
(Reporter: bniolet, Assigned: mternoway)
Details
Attachments
(1 file)
77.38 KB,
image/jpeg
|
Details |
>>Project/Request Title: Firefox OS Hungary launch email >>Project Overview: Hi gang. As expected, the Alcatel One Touch Fire E launched in Hungary. What was unexpected is that the partner *also* launched the Alcatel One Touch Fire C. We have a standard email we use for 2nd country launches. But because this one has two phones, we'd like to go with a new image for our email that shows both devices. >> Creative Help Needed: Copy: No Design: Yes Video: No Other: No >>Creative Specs: We need to replace this image from the email with one that shows both devices: http://image.e.mozilla.org/lib/fe9915707361037e75/m/2/Fox_phone_FireE.jpg Here's a screenshot of the full email: https://drive.google.com/file/d/0B2qkDGsZj9SzTW0ySnBQcHNVTEE/view?usp=sharing We can launch this email whenever we get the creative ready. >>CTA and Design: This is our standard 2nd launch email. Looking for a design that reflects the launch of the two phones. Alcatel One Touch Fire E Alcatel One Touch Fire C >>Creative Due Date: 2014-11-25 >>Launch Date: 2014-12-01 >>Mozilla Goal: Firefox OS >>Points of Contact: mthayer@mozilla.com, mjkelly@mozilla.com, jdavis@mozilla.com
Comment 1•10 years ago
|
||
Hi Ben, I'm waiting to hear back from Matt on his availability. I want to set a realistic expectation that the 25th may not be enough time, but will get back to you on that.
Assignee: jbalaco → mternoway
Status: NEW → ASSIGNED
hi guys, I've attached a hero graphic containing both the Fire C and E. Due to space and scale I've left out the fox overlay image. Here is an example of what it would look like within the email itself: http://cl.ly/image/180G1T3U1C1a MT
Reporter | ||
Updated•10 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•