Closed Bug 1032902 Opened 12 years ago Closed 11 years ago

Mozilla Services logo for branding

Categories

(Marketing :: Design, task)

All
Other
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
Due Date:

People

(Reporter: telliott, Assigned: jbalaco)

Details

>>Project/Request Title: Mozilla Services logo for branding >>Project Overview: We'd like to get a Services-team logo for use in branding (I think the first thing is likely to be polo shirts). We had one years ago, but it's no longer compatible with brand guidelines (if we can use the dinosaur with the bow tie, we're all for it!) (Note that the launch date below is pretty arbitrary. We have flexibility here) >> Creative Help Needed: Copy: No Design: Yes Video: No Other: No >>Creative Specs: Whatever we use with partners for logo work. >>CTA and Design: Something that plays up the cloud nature of the Services department seems like an obvious way to go. >>Creative Due Date: 2014-07-22 >>Launch Date: Not provided >>Mozilla Goal: Services >>Points of Contact: telliott@mozilla.com, mmayo@mozilla.com
Hey Toby. For internal teams, we typically just do wordmarks. Chris Beard has asked that we stick with Mozilla and Firefox as our primary logoed brands, and not dilute things further beyond that. Occasionally we'll do designs for specific events or gear needs (ex. bug 1032897), but if you need a way to represent the team in general I'd recommend the wordmark option.
Hi Toby, Just a ping to see if you are ok with John's note about getting a wordmark vs. a logo.
Flags: needinfo?(telliott)
Wordmark is fine. If we were doing polo-style shirts, is there a Mozilla logo we should use?
Flags: needinfo?(telliott)
Here are a couple of files you can use for shirts or pretty much anything else: png: http://cl.ly/image/3X090P182l2l eps: http://cl.ly/code/031809191V2X
Going to resolve this one since John provided the wordmarks above. Please let us know if you need anything else.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.