Closed Bug 1024766 Opened 10 years ago Closed 10 years ago

OSCON CTA Cards

Categories

(Marketing :: Design, task)

Product:
Marketing
Component:
Design
Platform:
All
Other
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED
Due Date:

People

(Reporter: rchau, Assigned: mternoway)

References

Details

Attachments

(1 file, 1 obsolete file)

OSCON_CTACards_PRINT.pdf
1.01 MB, application/vnd.pdf
Details 
>>Project/Request Title:
OSCON CTA Cards

>>Project Overview:
This is to be a series of business card- or trading card-sized cards that serve as short, quick reference cards about the main products and services that Mozilla offers, with short snippets of information and a URL to direct readers to for more information. 

These cards will be launched at OSCON 2014, but reused for many other events too. It would be a quick, fun way to get people to learn a bit more about what Mozilla offers (collect them all!), and more unique and intriguing than a traditional one-sheet, brochure, pamphlet, etc.



>> Creative Help Needed:
Copy:    Yes 
Design:  Yes 
Video:   No 
Other:  No

>>Creative Specs:
Trading card (like a baseball card), or business card shape - open to suggestion here
Deliverable: (6) unique designs as print-ready PDF files with 0.125" bleeds

Design #1:
Front Side:
- MDN branding (logo, color)
- "developer.mozilla.org" URL
Back Side:
- Short, 1-2 sentence blurb about what the Firefox OS Simulator is and how you (the developer) can use it
- "See more at" or "Learn more at" the mz.la short link that points to "https://developer.mozilla.org/en-US/docs/Tools/Firefox_OS_Simulator"

Design #2:
Front Side:
- MDN branding (logo, color)
- "developer.mozilla.org" URL
Back Side:
- Short, 1-2 sentence blurb about what the Firefox Browser Console is and how you (the developer) can use it
- "See more at" or "Learn more at" the mz.la short link that points to "https://developer.mozilla.org/en-US/docs/Tools/Browser_Console"

Design #3:
Front Side:
- MDN branding (logo, color)
- "developer.mozilla.org" URL
Back Side:
- Short, 1-2 sentence blurb about what the Firefox for Android remote debugging tools are and how you (the developer) can use them
- "See more at" or "Learn more at" the mz.la short link that points to "https://developer.mozilla.org/en-US/docs/Tools/Remote_Debugging/Firefox_for_Android"

Design #4:
Front Side:
- MDN branding (logo, color)
- "developer.mozilla.org" URL
Back Side:
- Short, 1-2 sentence blurb about what the Mozilla Developer Network is and how you can join.
- "See more at" or "Learn more at" the mz.la short link that points to "https://developer.mozilla.org/en-US/docs/Mozilla/Connect"

Design #5:
Front Side:
- Mozilla branding (logo, color)
- "https://www.mozilla.org/en-US/privacy/" URL
Back Side:
- Short, 1-2 sentence blurb about Mozilla's privacy principles, something like "Did you know Mozilla cares about YOUR privacy?" (this is aimed at users and developers)
- "See more at" or "Learn more at" the mz.la short link that points to our Privacy Principles page "https://www.mozilla.org/en-US/privacy/principles/"

Design #6:
Front Side:
- Firefox (logo, color)
- "firefox.com" URL
Back Side:
- Short, 1-2 sentence blurb about the new Australis, something like "Did you know Mozilla designed Australis with YOU in mind?" (this is aimed at users and developers)
- "See more at" or "Learn more at" the mz.la short link that points to "https://www.mozilla.org/en-US/firefox/desktop/"


>>CTA and Design:
CTA is to get people thinking about Mozilla's tools and products, using our developer tools, and downloading Australis.

>>Creative Due Date:
2014-07-01

>>Launch Date:
2014-07-20

>>Mozilla Goal:
Adoption of developer tools (Firefox OS, Firefox, and Firefox for Android)

>>Points of Contact:
sprasad@mozilla.com, bkerensa@gmail.com
Assignee: jbalaco → mternoway
Status: NEW → ASSIGNED
Hi all, I am currently in the works on a layout for the CTA cards and am wondering if someone can provide me with the shortened mz.la URLs for each of the backsides ?

Thanks,
Matt
(In reply to MT from comment #1)
> Hi all, I am currently in the works on a layout for the CTA cards and am
> wondering if someone can provide me with the shortened mz.la URLs for each
> of the backsides ?
> 
> Thanks,
> Matt

Are the mzl.la links right to use here? In my experience we don't tend to use them for things like this. For desktop, at least, we should use firefox.com/desktop and for privacy we could simply use mozilla.org/privacy (though maybe mozilla.org/privacy/you is a better destination URL?).

Whatever we use, let's make sure not to include "www" or the language code (en-us).

Thanks.
I agree with that approach for the general cards, Matej, but I'm not sure what we do with the specific dev tools' URLs (remote debugging, simulator, and console). Also the CTA for the MDN design is particularly directed to the "Connect" page of the MDN site, do you think directing to developer.mozilla.org will sufficiently convey the CTA here?
Flags: needinfo?(Mnovak)
(In reply to Robyn Chau from comment #3)
> I agree with that approach for the general cards, Matej, but I'm not sure
> what we do with the specific dev tools' URLs (remote debugging, simulator,
> and console). Also the CTA for the MDN design is particularly directed to
> the "Connect" page of the MDN site, do you think directing to
> developer.mozilla.org will sufficiently convey the CTA here?

Yup, that's a good point. And sorry, I didn't give comment 0 a close enough read. It makes sense to use the shortened URLs for the various developer pages, but otherwise we should have short enough URLs for the others.

What do you think about the privacy page? Which one do you want to use?

I also see stuff like this in comment 0: "Short, 1-2 sentence blurb about what the Firefox Browser Console is and how you (the developer) can use it"

Where can we get that info? What would you like to say about each? Could someone provide draft copy for those?

Thanks.
Flags: needinfo?(Mnovak)
Gotcha - here are the developer tools shortlinks:
Design #1: http://mzl.la/1nAEo7a 
Design #2: http://mzl.la/1nAEpYP
Design #3: http://mzl.la/UHcX3v 

I love the mozilla.org/privacy/you URL for the Privacy card, Design #5, feels very personal.

For the blurbs, I'm thinking the following folks might be able to help: Dave Camp and Jeff Griffiths for the Console blurb, Christian Heilmann for the Simulator, and Michelle Luna for Firefox for Android. 

Dave, Jeff, Christian, and Michelle, can you come up with a short 1-2 sentence blurb about the various items in the original bug description, based on your respective specialties, please? This is my first pass at folks who could contribute, please let me know if there's someone else who might be more appropriate.
Flags: needinfo?(mluna)
Flags: needinfo?(jgriffiths)
Flags: needinfo?(dcamp)
Flags: needinfo?(cheilmann)
Note, Michelle - the blurb request is specifically for the remote debugger, not Fx for Android in general.
(In reply to Robyn Chau from comment #5)
...
> Dave, Jeff, Christian, and Michelle, can you come up with a short 1-2
> sentence blurb about the various items in the original bug description,
> based on your respective specialties, please?

For this one:

Design #2:
Front Side:
- MDN branding (logo, color)
- "developer.mozilla.org" URL
Back Side:
- Short, 1-2 sentence blurb about what the Firefox Browser Console is and how you (the developer) can use it
- "See more at" or "Learn more at" the mz.la short link that points to "https://developer.mozilla.org/en-US/docs/Tools/Browser_Console"

...I don't understand how we got to focusing on the browser console for this. Who is the target audience for this, web developers? Add-on developers? Firefox team members?

Aside: as of Monday, the App Manager is now 'WebIDE'.
Flags: needinfo?(jgriffiths) → needinfo?(rchau)
(In reply to Jeff Griffiths (:canuckistani) from comment #7)
> (In reply to Robyn Chau from comment #5)
> ...
> > Dave, Jeff, Christian, and Michelle, can you come up with a short 1-2
> > sentence blurb about the various items in the original bug description,
> > based on your respective specialties, please?
> 
> For this one:
> 
> Design #2:
> Front Side:
> - MDN branding (logo, color)
> - "developer.mozilla.org" URL
> Back Side:
> - Short, 1-2 sentence blurb about what the Firefox Browser Console is and
> how you (the developer) can use it
> - "See more at" or "Learn more at" the mz.la short link that points to
> "https://developer.mozilla.org/en-US/docs/Tools/Browser_Console"
> 
> ...I don't understand how we got to focusing on the browser console for
> this. Who is the target audience for this, web developers? Add-on
> developers? Firefox team members?
> 
> Aside: as of Monday, the App Manager is now 'WebIDE'.

Hello Jeff,

The target audience is Web Developers for Design #2 although we do feel there could be some value to highlighting this tool to power users.
(In reply to Benjamin Kerensa [:bkerensa] from comment #8)
> The target audience is Web Developers for Design #2 although we do feel
> there could be some value to highlighting this tool to power users.

Do you instead mean the 'web console'? The Browser console delivers all logging messages from Firefox and might be most useful to add-on or Firefox develoeprs. The Web Console is in the devtools toolbox and only shows logs from the current web page, so IMO it is generally more useful to web developers.
I'll defer to Benjamin for this one.
Flags: needinfo?(rchau) → needinfo?(bkerensa)
(In reply to Jeff Griffiths (:canuckistani) from comment #9)
> (In reply to Benjamin Kerensa [:bkerensa] from comment #8)
> > The target audience is Web Developers for Design #2 although we do feel
> > there could be some value to highlighting this tool to power users.
> 
> Do you instead mean the 'web console'? The Browser console delivers all
> logging messages from Firefox and might be most useful to add-on or Firefox
> develoeprs. The Web Console is in the devtools toolbox and only shows logs
> from the current web page, so IMO it is generally more useful to web
> developers.

Yes "Web Console"
Flags: needinfo?(bkerensa)
FYI Christian is at Google I/O this week and may be delayed in getting back to this thread. Matej, is there a method by which you source SMEs when you craft official Mozilla copy? My instinct is to track down product leads, but it's tricky to get people's time these days.
Flags: needinfo?(Mnovak)
(In reply to Robyn Chau from comment #12)
> FYI Christian is at Google I/O this week and may be delayed in getting back
> to this thread. Matej, is there a method by which you source SMEs when you
> craft official Mozilla copy? My instinct is to track down product leads, but
> it's tricky to get people's time these days.

That entirely depends on what "SME" means. I've never heard that before.
Flags: needinfo?(Mnovak)
Oh sorry. "Subject matter expert."
(In reply to Robyn Chau from comment #14)
> Oh sorry. "Subject matter expert."

Ah, thank you.

I'll be honest, I'm not usually the one tracking people down, so I'm sure what the process is. I just want to make sure we're saying the right thing for the right audience.
Update: Dave will be providing the copy for Designs 2 and 3.
Flags: needinfo?(mluna)
Flags: needinfo?(dcamp)
Hi guys, 

I know we are still finalizing copy for this, but I realized I haven't shown any design yet. Here is a link to the direction I am thinking for these. http://cl.ly/image/2z2F0C1g163D .  Top row shows the front side of the various cards and bottom row is the back side.  All copy is place holder at the moment, but thought this could give a better indicator to the amount of space to work with.  You will see for the Firefox backside, I've included an option which focuses on the use of icons and power bars (like old Marvel trading cards). This might be a bit much and would take some extra massaging of content to work, but thought I'd throw it in there as an option.  Otherwise I think something simple like a logo, few lines and a CTA would do the trick nicely. For the MDN card, I realize there are 3 options for this...I haven't altered the design to make each distinct at this point, but perhaps the various copy for each would define the card enough?  Let me know what you think.

Thanks!
Matt
Hi Matt,

I love these!! I think they're really great and very eye-catching. I'm not sure about the power bars, while I love the look I'm not sure they'll convey clear messaging - John, what are your thoughts?

Thanks!
Flags: needinfo?(jslater)
Copy received from Dave re:Android remote debugger: "You can debug a page running in Firefox for Android using the complete suite of Firefox Developer Tools on your desktop."
Should we add a "Did you know?" ahead of this?
I love the look. Hard to say for sure on the power bars, as I'm not totally clear on the content needs here. I will say that I think they *could* work, but also that they're probably not essential. It may come down to how much time we have to play around with that content.

Should we be using the blueprint background for the developer one?
Flags: needinfo?(jslater)
I also like the overall look of each CTA Card but the bars are a bit confusing to me. The blueprint background on the MDN/Dev CTA might look nice too.
Thanks for the feedback. I've added in the subtle grid background for the MDN card. I think it ties it in closer to the MDN brand. Since there will be 3 different MDN cards, we ok with having just the copy define each of those, or is there a need to visually define them as well?

http://cl.ly/image/00211w3z0y08

With regards to the bars, I think I was creating an unnecessary problem...got caught up in trading card nostalgia :S
(In reply to MT from comment #22)
> Thanks for the feedback. I've added in the subtle grid background for the
> MDN card. I think it ties it in closer to the MDN brand. Since there will be
> 3 different MDN cards, we ok with having just the copy define each of those,
> or is there a need to visually define them as well?
> 
> http://cl.ly/image/00211w3z0y08
> 
> With regards to the bars, I think I was creating an unnecessary
> problem...got caught up in trading card nostalgia :S

The last link has a placeholder PNG Icon but not the updated mockup.
Oops, thanks for catching.

http://cl.ly/image/3X2x2d451C3i
+1 on this latest revision it really looks crisp
Met with Stormy, Shez, and Benjamin today - consensus was that we should go with one MDN design, instead of four, and just provide very short links and blurbs about the main tools listed in Designs 1-3 (Remote Debugger, Web Console, Simulator). 

So that should leave us with 1 Firefox card, 1 MDN card, and 1 privacy card.
One last bit is Stormy had feedback that she would like to see somewhere on the card "OSCON 2014" she thinks this will add the benefit of making it feel collectable.
(In reply to Benjamin Kerensa [:bkerensa] from comment #27)
> One last bit is Stormy had feedback that she would like to see somewhere on
> the card "OSCON 2014" she thinks this will add the benefit of making it feel
> collectable.

I think that's easy enough to incorporate, but based on the following instruction in comment 0 we thought these are supposed to live on beyond this one event:

"These cards will be launched at OSCON 2014, but reused for many other events too."

Can you confirm? Thanks.
(In reply to Matej Novak [:matej] from comment #28)
> (In reply to Benjamin Kerensa [:bkerensa] from comment #27)
> > One last bit is Stormy had feedback that she would like to see somewhere on
> > the card "OSCON 2014" she thinks this will add the benefit of making it feel
> > collectable.
> 
> I think that's easy enough to incorporate, but based on the following
> instruction in comment 0 we thought these are supposed to live on beyond
> this one event:
> 
> "These cards will be launched at OSCON 2014, but reused for many other
> events too."
> 
> Can you confirm? Thanks.

Hi Matej,

So I definately think based on discussions we have had with the rest of Dev Rel that they do want to re-use these CTA's for other events so I guess our hope is if we can have a generic template which Dev Rel would use more generally and have one with OSCON 2014 on the card wherever it may be appropriate.
+1 to Comment 29. The idea Stormy was thinking of is that the CTA cards could be kind of collector's items, and that this round would have OSCON 2014 on them, and we simply swap out that event name for the next event name (say, BrazilJS 2014).
Simulator copy: The simulator creates an emulated phone right on your desktop machine and allows you to build and test apps without having to have one.

Not sure if this would be too long to include on the MDN card with the remote debugger and web console blurbs?
Flags: needinfo?(cheilmann) → needinfo?(Mnovak)
For Privacy perhaps...

"Did you know Mozilla was recognized as the most trusted Internet Company for Privacy"

https://blog.mozilla.org/blog/2013/01/28/privacy-day-2013/

Lets see if we can get feedback from Sid Stamm but I think this is a good highlight.
(In reply to Benjamin Kerensa [:bkerensa] from comment #32)
> For Privacy perhaps...
> 
> "Did you know Mozilla was recognized as the most trusted Internet Company
> for Privacy"

I'd be cautious about this (especially given all the churn in this space, people may not agree with this claim), but adding the year to the statement may make a nice nugget of info.

Some ideas:

Do we want something about Do Not Track?[0]  We could make a card with something about how Mozilla helped pioneer the Do Not Track feature to give web users a voice in how their data is collected and used...  We could also make a card about Lightbeam (the addon formerly known as collusion).

Or feature-wise, we could make a card about private browsing mode in Firefox.[1]  :)

For security, we could identify our security bug bounty program (we pay security researchers for their security bugs) or make a card for Content Security Policy (a feature that lets web devs secure their site[2]).

[0] http://www.mozilla.org/en-US/dnt/
[1] https://support.mozilla.org/en-US/kb/private-browsing-browse-web-without-saving-info
[2] https://developer.mozilla.org/en-US/docs/Web/Security/CSP/Introducing_Content_Security_Policy
(In reply to Sid Stamm [:geekboy or :sstamm] from comment #33)
> (In reply to Benjamin Kerensa [:bkerensa] from comment #32)
> > For Privacy perhaps...
> > 
> > "Did you know Mozilla was recognized as the most trusted Internet Company
> > for Privacy"
> 
> I'd be cautious about this (especially given all the churn in this space,
> people may not agree with this claim), but adding the year to the statement
> may make a nice nugget of info.
> 
> Some ideas:
> 
> Do we want something about Do Not Track?[0]  We could make a card with
> something about how Mozilla helped pioneer the Do Not Track feature to give
> web users a voice in how their data is collected and used...  We could also
> make a card about Lightbeam (the addon formerly known as collusion).
> 
> Or feature-wise, we could make a card about private browsing mode in
> Firefox.[1]  :)
> 
> For security, we could identify our security bug bounty program (we pay
> security researchers for their security bugs) or make a card for Content
> Security Policy (a feature that lets web devs secure their site[2]).
> 
> [0] http://www.mozilla.org/en-US/dnt/
> [1]
> https://support.mozilla.org/en-US/kb/private-browsing-browse-web-without-
> saving-info
> [2]
> https://developer.mozilla.org/en-US/docs/Web/Security/CSP/
> Introducing_Content_Security_Policy

Thanks for that feedback Sid. Something on DNT would work if you want to give a small blurb there we are really trying to highlight how much Mozilla values user privacy.
Flags: needinfo?(sstamm)
Sorry for the delay, I was at a conference last week and a bit busy.

How about: 
"Do Not Track (a feature in Firefox) allows you to tell websites you don't like third-party tracking, including behavioral advertising. Learn more at [url]"

[url] https://www.mozilla.org/dnt/
Flags: needinfo?(sstamm)
Hi team,

The printer will need the design ASAP - can we send over the Firefox and the Privacy cards by EOD today? 

For the MDN card, here are the options I'm seeing:
1) We have one liners and short URLs for the remote debugger, the web console, and for the simulator on the back of the card. Concern: still need copy, also would be cramped to include this text in the card space.
2) We have the MDN card feature a URL that points to a wiki page that highlights these three tools and has the space for the blurbs as well.
3) We have the MDN card feature the overall tools page https://developer.mozilla.org/en-US/docs/Tools.

Stormy, Benjamin, what do you think? Also, this can just be for OSCON, we can adjust the design for future iterations of this card, we just need to get a design out the door today.
Thanks!
Flags: needinfo?(stormy)
Flags: needinfo?(bkerensa)
I like what we have +1
Flags: needinfo?(bkerensa)
Sorry for the delayed response here.

Robyn, any chance you could put all the copy you need me to review into a single comment to make sure I'm looking at the latest and correct versions?

Thanks.
Flags: needinfo?(Mnovak)
Flags: needinfo?(rchau)
Sure thing Matej, had to take a minute and grab it all myself. Here's my suggestion, based on this thread and separate email threads:

Ref Matt's latest mockup: http://cl.ly/image/3X2x2d451C3i 
Front of cards: 
- Tabzilla
- relevant logo
- "OSCON 2014" copy at bottom

Back of cards:
- relevant wordmark
- blurb
- URL

Firefox blurb: How you use the Web is unique. Firefox lets you change it to match. Remove what you don’t use, keep what you do and put it just about anywhere you want. 
Learn more at https://www.mozilla.org/firefox/desktop/

MDN blurb: Create, explore, debug, and more using Mozilla's developer tools for desktop and mobile. 
Learn more at https://developer.mozilla.org/tools

Privacy blurb: Do Not Track (a feature in Firefox) allows you to tell websites you don't like third-party tracking, including behavioral advertising. 
Learn more at https://www.mozilla.org/dnt


How do these sound?
Flags: needinfo?(rchau)
Flags: needinfo?(bkerensa)
Flags: needinfo?(Mnovak)
Works for me.
Flags: needinfo?(bkerensa)
Thanks, Robyn. That helps a lot. Here are my edits:

Firefox blurb: 
How you use the Web is unique. Firefox lets you change it to match. Remove what you don’t use, keep what you do and put it just about anywhere you want. 
Learn more at firefox.com/desktop

MDN blurb: 
Create, explore, debug and more using Mozilla developer tools for desktop and mobile. 
Learn more at developer.mozilla.org/tools

Privacy blurb (v1): 
Do Not Track is a feature in Firefox that helps put you in control of the way your information is collected and used online. 
Learn more at mozilla.org/dnt

Privacy blurb (v2): 
Do Not Track, a Firefox feature, lets you tell websites that you want to opt out of tracking for purposes like behavioral advertising.
Learn more at mozilla.org/dnt

(Two versions of the privacy blurb above. I prefer v1.)
Flags: needinfo?(Mnovak)
(In reply to Matej Novak [:matej] from comment #41)
> Thanks, Robyn. That helps a lot. Here are my edits:
> 
> Firefox blurb: 
> How you use the Web is unique. Firefox lets you change it to match. Remove
> what you don’t use, keep what you do and put it just about anywhere you
> want. 
> Learn more at firefox.com/desktop
+1

> MDN blurb: 
> Create, explore, debug and more using Mozilla developer tools for desktop
> and mobile. 
> Learn more at developer.mozilla.org/tools
+1
 
> Privacy blurb (v1): 
> Do Not Track is a feature in Firefox that helps put you in control of the
> way your information is collected and used online. 
> Learn more at mozilla.org/dnt
> 
> Privacy blurb (v2): 
> Do Not Track, a Firefox feature, lets you tell websites that you want to opt
> out of tracking for purposes like behavioral advertising.
> Learn more at mozilla.org/dnt
> 
> (Two versions of the privacy blurb above. I prefer v1.)
I prefer v1 too. Benjamin?
Flags: needinfo?(bkerensa)
V1
Flags: needinfo?(bkerensa)
Hi All, 

Just doing some bug clean-up and wanted to find out what else is needed from the Creative Team on this one. If you're all set, please go ahead and resolve.

Thanks!
Jennifer
(In reply to Jennifer Balaco from comment #44)
> Hi All, 
> 
> Just doing some bug clean-up and wanted to find out what else is needed from
> the Creative Team on this one. If you're all set, please go ahead and
> resolve.
> 
> Thanks!
> Jennifer

Hi Jennifer,

I think we are still waiting for the final deliverable so we can print by end of day.
Hi Matt - are we good to go with print-ready versions to send to the printer today? He'll need them by 1p PT for an on-time delivery. Thanks!
Flags: needinfo?(mternoway)
Attached file OSCON_CTACards_PRINT.pdf (obsolete) — 
Hey Robyn, here is the print ready PDF.  I've included latest copy as well as URLs. If everyone is ok with this...it's good to go.
Flags: needinfo?(mternoway)
Should the URLs on the front be the more general ones that go with the logo shown and then save the more detailed URLs for the back?

Firefox — firefox.com
MDN — developer.mozilla.org
Mozilla — mozilla.org

Either way, let's change the CTA line to one of the following:

Learn more at
[URL GOES HERE]

OR

Learn more:
[URL GOES HERE]

(i.e. it should have "at" or a colon, but not both)
Thanks Matej. That makes sense to me for the front...since it's the general logo.  As for the back, I like 'Learn more at'.
I like "Learn more at" too. Also, I think we were going to have "OSCON 2014" at the bottom of the front of each card, yes?
Flags: needinfo?(mternoway)
Flags: needinfo?(Mnovak)
(In reply to Robyn Chau from comment #50)
> I like "Learn more at" too. Also, I think we were going to have "OSCON 2014"
> at the bottom of the front of each card, yes?

That's totally up to you. I wasn't sure where we landed on that, but I do think it's better to have the name of the even rather than URLs on both sides.
Flags: needinfo?(Mnovak)
Flags: needinfo?(stormy)
We could make these short urls and then we could track how many people actually visited them, e.g.  mzl.la/devtools. I added Luke Crouch who can generate them.
(In reply to Robyn Chau from comment #50)
> I like "Learn more at" too. Also, I think we were going to have "OSCON 2014"
> at the bottom of the front of each card, yes?

If we are to include OSCON 2014 or similar, it would make sense to use their branded wordmark. I've seen it a few ways though, and unable to track down an official vector version. Is this something we have access to?
Flags: needinfo?(mternoway)
(In reply to MT from comment #53)
> (In reply to Robyn Chau from comment #50)
> > I like "Learn more at" too. Also, I think we were going to have "OSCON 2014"
> > at the bottom of the front of each card, yes?
> 
> If we are to include OSCON 2014 or similar, it would make sense to use their
> branded wordmark. I've seen it a few ways though, and unable to track down
> an official vector version. Is this something we have access to?

We do not and by the time we got a response from O'Reilly it could push us past the 1PM PST deadline for print
Just had a call with the OSCON organizers - we do NOT have the rights to use the official OSCON wordmark.

Also, Stormy - not sure if there is a way to generate the appropriate tracking URL for each of these by the time these need to get to the printer. Luke and I had a brief IRC chat today and there were some snags, NI'ing him to be sure.
Flags: needinfo?(lcrouch)
So we are pointing not to Do Not Track, but mozilla.org, and not to the Tools page, but to the MDN page, correct?
Short url's for tracking could/would be:

Firefox: mzl.la/oscon14-firefox to https://www.mozilla.org/firefox/new/
MDN: mzl.la/oscon14-mdn to https://developer.mozilla.org
Mozilla: mzl.la/oscon14-mozilla to https://www.mozilla.org/

Robyn/Benjamin - approve?
Flags: needinfo?(rchau)
Flags: needinfo?(lcrouch)
Flags: needinfo?(bkerensa)
Looks good to me! Requesting Stormy's approval as well.
Flags: needinfo?(rchau) → needinfo?(stormy)
(In reply to Luke Crouch [:groovecoder] from comment #57)
> Short url's for tracking could/would be:
> 
> Firefox: mzl.la/oscon14-firefox to https://www.mozilla.org/firefox/new/
> MDN: mzl.la/oscon14-mdn to https://developer.mozilla.org
> Mozilla: mzl.la/oscon14-mozilla to https://www.mozilla.org/
> 
> Robyn/Benjamin - approve?

I actually think on the back we should point to the specific things we're talking about (/desktop, /tools, /dnt). Otherwise we're making users do a lot more work to find them.

Those shortened URLs also aren't very friendly for users to have to type manually (which could skew any potential testing). I would strongly recommend we keep the URLs in comment 41.
+1 that the URLs are cleaner, however at this point we'll have to sacrifice one goal over another: visual or tracking. I'll ask Stormy to make the call on this one, as she's the Accountable on this event. 

My two cents: I'd go with a mzl.la link to track the /dnt, /tools, and /desktop hits for the event, as understanding the impact we have at OSCON is a priority, and this is a casual and web creator audience who I don't think would mind an extra couple of keystrokes, esp as these tracker URLs make logical sense without being annoying (ie. vs. mzl.la/ase87agh2). If the audience were more marketing or executive-targeted, I'd stick to the straightforward ones, but I'm voting for the tracker URLs.
(In reply to Robyn Chau from comment #60)
> +1 that the URLs are cleaner, however at this point we'll have to sacrifice
> one goal over another: visual or tracking. I'll ask Stormy to make the call
> on this one, as she's the Accountable on this event. 
> 
> My two cents: I'd go with a mzl.la link to track the /dnt, /tools, and
> /desktop hits for the event, as understanding the impact we have at OSCON is
> a priority, and this is a casual and web creator audience who I don't think
> would mind an extra couple of keystrokes, esp as these tracker URLs make
> logical sense without being annoying (ie. vs. mzl.la/ase87agh2). If the
> audience were more marketing or executive-targeted, I'd stick to the
> straightforward ones, but I'm voting for the tracker URLs.

In that case, let's make sure they're pointing to the correct URLs:
mozilla.org/dnt
developer.mozilla.org/tools
firefox.com/desktop (which redirects to mozilla.org/firefox/desktop)

Thanks.
It pains me to make a decision that would lose us metrics but I agree that the benefit of tracking is not worth losing the mozilla.org branding. mzl.la is kind of ugly on a card.

Now, if we'd gone with the one page for OSCON that had the 3 links off of it, we could have a beautiful url for that, track hits to that page and then have mzl links off of it. Next time!
Flags: needinfo?(stormy)
Okay, so to be clear: I *WILL NOT* create mzl.la short-links for these.

Robyn and I already discussed that we *can* measure Portland-based traffic on mozilla.org and developer.mozilla.org during OSCON to get an overall sense of how effective our presence is.

But for future events, I agree - a nice event-specific landing page will do best.
Noted for the future! So, Matt, for this set of cards, we'll go with:

mozilla.org/dnt
developer.mozilla.org/tools
firefox.com/desktop

Thanks for the quick turnaround on the discussion, all!
Flags: needinfo?(mternoway)
Excellent. Here is an example of where we are at with the info and layout:

http://cl.ly/image/0q3X1u2O2a3u

If all is considered final, I can post the print ready PDF.
Flags: needinfo?(mternoway)
I love it. Benjamin?
I think Benjamin is offline - in the interest of time I say we move forward.
Hi guys, attached is the updated print ready PDF for the CTA cards.

Let me know if there are any issues.

Thanks,
MT
Attachment #8456269 - Attachment is obsolete: true
+1 from albeit late
Flags: needinfo?(bkerensa)
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.

Attachment

General

Creator:
Created:
Updated:
Size: