Closed
Bug 744956
Opened 13 years ago
Closed 13 years ago
Design of Email Archive
Categories
(Marketing :: Design, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jdavis, Assigned: tyronflanagan)
References
Details
(Whiteboard: Due: 5/31)
Attachments
(3 files, 1 obsolete file)
Hello Creative!
We're working on creating an email Archive to host all past email newsletters of Firefox and You (Bug 731405 - [Q2 Tracking Bug] Add Email Newsletter Archive to mozilla.org/firefox )
Right now the Archive mock up is based on the current Firefox & You Email Template - but it needs a makeover to match the new One Mozilla look.
Can you assist?
Goal mockup deadline: May 31
Comment 1•13 years ago
|
||
Looping in Ty. He's busy with Apps related work right now but I think May 31st deadline is very doable.
Assignee: tshahian → tyronflanagan
Status: NEW → ASSIGNED
Whiteboard: Due: 5/31
| Assignee | ||
Comment 2•13 years ago
|
||
Quick question – Where will this page live within the site? Will it be included within the PRESS CENTER or PARTICIPATES section perhaps?
| Reporter | ||
Comment 3•13 years ago
|
||
The exact location is TBD, but in the dev bug (https://bugzilla.mozilla.org/show_bug.cgi?id=731405) the current idea is to create a new page:
http://www.mozilla.org/en-US/newsletter/archive
I'm not 100% clear how it would be linked to other than on the newsletter sign up page.
Updated•13 years ago
|
| Reporter | ||
Comment 4•13 years ago
|
||
Design requirement:
last 3 or 4 emails have more relevance (rather than just a bulleted list); so people can find the latest emails faster
| Assignee | ||
Comment 5•13 years ago
|
||
| Reporter | ||
Comment 6•13 years ago
|
||
This looks awesome! Can you send me the psd?
| Assignee | ||
Comment 7•13 years ago
|
||
Made a few adjustments to the design
Attachment #631504 -
Attachment is obsolete: true
| Assignee | ||
Comment 8•13 years ago
|
||
| Reporter | ||
Comment 9•13 years ago
|
||
Perfect - Thanks!
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•