[Social APICampaign] generic promo graphic - blogs, emails, etc.

RESOLVED FIXED

Status

RESOLVED FIXED
6 years ago
6 years ago

People

(Reporter: tshahian, Assigned: jboriss)

Tracking

(Blocks: 1 bug)

Details

Attachments

(11 attachments)

Comment hidden (empty)
(Reporter)

Updated

6 years ago
Assignee: tshahian → mternoway
Blocks: 805242
(Reporter)

Updated

6 years ago
Blocks: 810351
(Reporter)

Updated

6 years ago
Summary: [Social APICampaign] graphic for moz.blog announcement → [Social APICampaign] generic promo graphic - blogs, emails, etc.
(Reporter)

Comment 1

6 years ago
Lee has done a few promo graphics that can be used for the moz.blog announcement post, and elsewhere.  Please review the attachments and let us know if there is anything missing.  There are 3 options.

Comment 2

6 years ago
Created attachment 681241 [details]
SocialAPI blog graphic 1 - 620 x 350

version 1

Comment 3

6 years ago
Created attachment 681242 [details]
SocialAPI blog graphic 2 - 620 x 350

version 2

Comment 4

6 years ago
Created attachment 681243 [details]
SocialAPI blog graphic 3 - 620 x 350

version 3

Comment 5

6 years ago
Linking to the PSD here, in case anyone needs it:
http://cl.ly/3m1D400b3h05

Comment 6

6 years ago
* PLEASE DISREGARD COMMENTS 2 THROUGH 4 - I need to make a small revision.

Comment 7

6 years ago
Linking final PSD and revised graphics here: http://cl.ly/2P1K3g190t3B

- these supercede comments 2-4
- assets are 620 x 350 px
(Reporter)

Comment 8

6 years ago
THANKS! closing.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED

Comment 9

6 years ago
These look awesome! For press, we will also need the full screenshot to embed in blog posts. I think graphic 2 shows chat and the jewels and the sidebar well so is it possible to get get a high resolution and web version of that screenshot? 

We will put both the promotional graphic and screenshot on the press center.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(Reporter)

Comment 10

6 years ago
Thanks Erica!  we do have that screenshot (which we've referred to as the 'hero' image) in a separate bug and will be able to share that as well.  I'll ask Lee or Ty if he can help with that.  

Fwiw, I don't think these graphics will be print-ready.  So, definitely not 300 dpi level but should work if it's not blown up too big.
(Reporter)

Updated

6 years ago
Assignee: mternoway → ltom

Comment 11

6 years ago
Ill have something readied in the AM for you Erica :)
(Reporter)

Comment 12

6 years ago
you rock, thank you.
Assignee: ltom → tyronflanagan

Comment 13

6 years ago
Ty- You do rock as Tara states, and I'm honored you still work with me after that graph that we won't talk about ever again ;)
(Reporter)

Comment 14

6 years ago
Handing this to Lee - Lee thank you very much.
Assignee: tyronflanagan → ltom
(Reporter)

Comment 15

6 years ago
back to Ty... sorry.
Assignee: ltom → tyronflanagan
(Reporter)

Comment 16

6 years ago
Erica, do you still need the requested screenshot in comment #9 for next week? I'm assuming not - please confirm.

Comment 17

6 years ago
We do still need the screenshot for the blog post
(Reporter)

Comment 18

6 years ago
Ok, can you confirm what this screenshot is though?  The one I was going to offer was the hero shot that was a core element to all the different creative we produced for the bigger marketing push which has now been dialed back / pushed back.  I would prefer that we don't use that here if we're not releasing all the assets along with it

Comment 19

6 years ago
(In reply to Tara (musingt) from comment #18)
> Ok, can you confirm what this screenshot is though?  The one I was going to
> offer was the hero shot that was a core element to all the different
> creative we produced for the bigger marketing push which has now been dialed
> back / pushed back.  I would prefer that we don't use that here if we're not
> releasing all the assets along with it

Erica -- I'll defer to your preference. Here's my two cents:

I'm fine with PR using the basic Etsy screenshot stripped down with otherwise no marketing messaging/enhancements. 

From the PMM perspective I support using that basic screenshot as a option since I don't think using it in the press now will diminish its ability to convert our users once it is launched more widely.
(Reporter)

Comment 20

6 years ago
Thanks LoFo.

The reality is that the Etsy screenshot was our hero and it's not a mere stripped down version of the image we had produced... it *is* the image we spent hours and hours on to craft for purposes of a bigger launch.


Erica, how about we use the same screenshot we had used before the the newsletter? I sent it to your inbox. and will attach shortly.

Sorry to be a pest, but I really would hate to use this hero shot that we spent so much time on in such an isolated (if not diminished) capacity when it was meant for something much bigger. 

I think the above screenshot would suffice and it has already been approved by facebook.

Erica wdyt?
(Reporter)

Comment 21

6 years ago
Created attachment 682555 [details]
about:mozilla screenshot
(Reporter)

Comment 22

6 years ago
we can also offer an alt version of the hero, perhaps cropped or presented some other way.  I'm speaking with Ty.... stay tuned.
(Reporter)

Comment 23

6 years ago
Ok, I spoke to Ty as well.

My understanding is that we're not making a marketing push for this feature on Tuesday, although we will have some PR efforts around it.

The Etsy image we produced is not a mere screenshot - it was a custom crafted image with many hours of work behind it - it was built for a larger campaign and, again, is the hero element of that campaign.  I'm not entirely sure what the scope of the blog post is, but If this image is isolated from the campaign and presented in this way, it will really lose it's value and be less exciting once we do choose to go live with it. 

So, my recommendation is to use the attached image (screenshot with soccer game) or create a similar screenshot that is not our Etsy hero for purposes of Tuesday's blog post.

Comment 24

6 years ago
This is the exact same screenshot as we used in beta - we need something different than what we used here: https://blog.mozilla.org/futurereleases/2012/10/22/help-us-test-the-social-api-with-facebook-messenger-for-firefox/

I requested in beta and someone was working on it, but all I need are (ideally) two different screenshots (can be on Mozilla properties) showing the social functionality. Because of privacy concerns, it's really hard for any press to make screenshots to use in their stories.
(Reporter)

Comment 25

6 years ago
Thanks Erica.  So then lets create a new screenshot.

Who created the one that you pointed to? Can't we have the same person produce 2 alt versions of the screenshot - and have them be, as you suggested, on our own properties? If it's a basic screenshot then I don't think we need a design bug for it. Unless I'm misunderstanding.

Comment 26

6 years ago
Laura - who did you have helping us before and how can we best get this done now?

Comment 27

6 years ago
(In reply to Erica Jostedt from comment #26)
> Laura - who did you have helping us before and how can we best get this done
> now?

Boriss created that first screenshot. She also created a different version at that time that includes a feature we're not shipping with, so that's not an option. The Etsy example originally created for this purpose also isn't an option since Pete want's that to wait for the consumer campaign. This is why we need a new asset at the last minute. 

I'm assigning this bug to Boriss to help create a different version of the "watching a Soccer game screenshot."

Creative Direction for Boriss:
We'd love your help here to design a similar chat example to the original one you created. 

-Please show the "State of Mozilla" landing page here: http://www.mozilla.org/en-US/foundation/annualreport/2011/ 
- Please show two people chatting about the State of Mozilla 
- Perhaps they're having a conversation about how to get involved with Mozilla
- Please make sure all information is privacy protecting, and use fake accounts, just like your original version did. 
- Please post to this bug when you're done

Timing: Erica -- when do you need this by? Please let Boriss know. 

Thanks for this last minute help!
Assignee: tyronflanagan → jboriss
(Assignee)

Comment 28

6 years ago
Created attachment 683352 [details]
Mockup: Chat open with Mozilla Annual Report in background

Comment 29

6 years ago
Thanks Boriss!

Please remove the "Like" icon from the URL bar since it's been removed from the product.
(Assignee)

Comment 30

6 years ago
Created attachment 683356 [details]
Mockup: Chat open with Mozilla Annual Report in background (community image, 2012 instead of 2011, no Google)

Adding another version in response to feedback.  Changes are:

- Report says 2012 instead of 2011
- Community photos rather than text displayed
- Blanked out Google favicon and name from search bar
(Assignee)

Comment 31

6 years ago
Created attachment 683357 [details]
Mockup: Chat open with Mozilla Annual Report in background (no like button, 2011 report)

This version:
- No Like button in toolbar
- Back to 2011 annual report in title and in URL bar
(Assignee)

Comment 32

6 years ago
Created attachment 683382 [details]
Mockup: With image of Akimbo Leo
(Assignee)

Comment 33

6 years ago
Created attachment 683383 [details]
Mockup: With image of Emerging Communities
(Assignee)

Comment 34

6 years ago
Created attachment 683394 [details]
Mockup: With Mary's photo at forefront

Comment 35

6 years ago
Created attachment 683437 [details]
Mockup: Boriss Final Sans "Like" and "2011" in URL

Comment 36

6 years ago
I've just submitted the graphic in Comment 35 to FB Brand Permissions via case BPR492428.

Erica -- please let your PR contact know and they can either give us their blessing or help expedite its approval.

Comment 37

6 years ago
Perfect- thank you!!
Status: REOPENED → RESOLVED
Last Resolved: 6 years ago6 years ago
Resolution: --- → FIXED
(Reporter)

Comment 38

6 years ago
Erica do you no longer need the screenshot that was meant for the consumer facing campaign? If not, we can keep this closed.  If you do - we need to reopen...
You need to log in before you can comment on or make changes to this bug.