Clean wordmark logo for Mozilla Research



4 years ago
4 years ago


(Reporter: larsberg, Assigned: Tara (musingt))





4 years ago
>>Project/Request Title:
Clean wordmark logo for Mozilla Research

>>Project Overview:
Part of the Mozilla Research team is traveling to asia and wanted new business cards. The back designs available were all either Firefox-related or not suitable for that environment (more formal). I was hoping for something that we could use that would be a cleaner design, even if it was just "mozilla" or "mozilla research" as a wordmark at appropriate scale and locations.

We created a quick plain mozilla one that we can use if the design team is too busy right now, so there's a fallback, but it doesn't look even as good as the ones in the "demo" business card images on the site (which you can't select):

>>Creative Specs & Deliverables:
Graphic file that we can upload to the business card printer. The design rules, formats, and outlines are available on the business card intranet page:

Secondary goal would be a nice logo image that we could use elsewhere, similar to the images available on the branding site, but that's not required and only if it popped out for free:

>>Launch Date:

>>Creative Due Date:

>>Mozilla Goal:
Mozilla Research

>>Points of Contact:

Comment 1

4 years ago
Thanks, we'll be back in touch on this soon. Just to confirm, you'd be ok with a card backside that read Mozilla Research?

Comment 2

4 years ago
Thanks - that would be fabulous, if it's not too much work!


4 years ago
Due Date: 2013-11-11 → 2013-10-21

Comment 3

4 years ago
We've tracked down a card backside that we can use, so no need to take up design time on this. Thanks!
Last Resolved: 4 years ago
Resolution: --- → WONTFIX

Comment 4

4 years ago
Ok, thanks!
lbergstrom: can you post the link or other reference for the backside you ended up tracking down?

Comment 6

4 years ago
pnkfelix: There's the one that dherman uses:

I also made up a dino version, but haven't had a chance to try it on a real card yet:
You need to log in before you can comment on or make changes to this bug.