Closed Bug 984192 Opened 11 years ago Closed 11 years ago

[Australis] Community Toolkit - /Community/ Blog Post & Email (Copy)

Categories

(Marketing :: Copy, task)

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

Tracking

(Not tracked)

Status:
RESOLVED FIXED
Due Date:

People

(Reporter: lizzn, Assigned: tpalmer)

References

Details

>>Project/Request Title: [Australis] Community Toolkit - /Community/ Blog Post & Email (Copy) >>Project Overview: Placeholder for /community/ blog post & email copy >>Creative Specs & Deliverables: Copy for https://blog.mozilla.org/community/ and community email >>Launch Date: Not provided >>Creative Due Date: 2014-04-15 >>Mozilla Goal: Firefox Deskop >>Points of Contact: ARRAY(0x7f0c09ab8200)
Assignee: jbalaco → Mnovak
Blocks: 984169
Due Date: 2014-04-15
Component: Design → Copy
Blocks: 984193
Hey Matej - this copy should be in line with the other assets for the community toolkit (bug 984189, bug 984190). I'm thinking we can co-opt the copy for the Mobilizer/Reps/FSA email(s) that's outlined in Bug 984193. LMK if you need more direction at all.
Reviewing this bug, I think we're going to need a little more info before we can get started. It actually feels like two separate things: 1. The blog post — Who will actually post it? Will that be David Boswell? I'm not sure what the vision is for that post (i.e. what we want to say to community about the new version of Firefox). Is it a download message? Will we encourage them to spread the word? It would be great if whoever is going to post that could write a draft and we could edit and plug in the appropriate text from other assets as needed. 2. The email — If this is supposed to be similar to (or even the same as) the blog post, we could just reuse that. Or could this be based on the one-off newsletter to users (bug 981189)? It would also be helpful to know what the distribution channel is (is this going to the Mozillians list?). I'll probably have Troy help with this, but we need some clarity on the above. Thanks.
(In reply to Matej Novak [:matej] from comment #2) > Reviewing this bug, I think we're going to need a little more info before we > can get started. It actually feels like two separate things: > > 1. The blog post — Who will actually post it? Will that be David Boswell? > I'm not sure what the vision is for that post (i.e. what we want to say to > community about the new version of Firefox). Is it a download message? Will > we encourage them to spread the word? It would be great if whoever is going > to post that could write a draft and we could edit and plug in the > appropriate text from other assets as needed. > This is a request from Gen for Community Engagement, so he should be able to clarify. My understanding is that it can use the same messaging as other community and user-based communications (emails, etc). > 2. The email — If this is supposed to be similar to (or even the same as) > the blog post, we could just reuse that. Or could this be based on the > one-off newsletter to users (bug 981189)? It would also be helpful to know > what the distribution channel is (is this going to the Mozillians list?). Same as above. I would say yes, it could be based off of the newsletter to users, as that's what we have discussed previously. But beyond that, I defer to Gen. > > I'll probably have Troy help with this, but we need some clarity on the > above. > > Thanks.
Gen, please let us know on the above. Even though this will use the same messaging, the tone and direction will be different. It would be really helpful to get some kind of outline for the blog post that we could work from. Thanks so much.
Gen, please see above. Thanks!
Flags: needinfo?(gen)
(In reply to Matej Novak [:matej] from comment #4) > Gen, please let us know on the above. Even though this will use the same > messaging, the tone and direction will be different. It would be really > helpful to get some kind of outline for the blog post that we could work > from. Thanks so much. Hi Matej, Lizz, This is the copy that we would want for Mozilla communities to use on their own sites or to localize regarding Australis. Imagine the Philippines community- this would be posted to their Mozilla Philippines blog about Australis, encouraging their community to download and use Australis. In terms of length, I'm not sure exactly but no more than a few paragraphs? Something short enough to read quickly but long enough for us to give our pitch effectively?
Flags: needinfo?(gen)
Thanks, Gen. That helps a lot. Assigning this one to Troy as well. We should be able to base it on bug 981189, maybe even use that text verbatim.
Assignee: Mnovak → troy
Hi Gen, Here's the final copy (and design) for the launch email: https://bugzilla.mozilla.org/attachment.cgi?id=8408958 Can you have a look and let us know if that works for your purposes as well? Thanks.
Flags: needinfo?(gen)
Matej, looks great to me. Also adding Mardi, Brian.
Flags: needinfo?(gen)
In the interest of cleaning up our Australis to-do bug list, I'm going to close this one but we can definitely reopen if Mardi or Brian have comments.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Looks good to me, thanks. Is the copy and/or coding for this available anywhere? Basically we just need a simple format that communities can localise and run with.
(In reply to Brian King [:kinger] from comment #11) > Looks good to me, thanks. > > Is the copy and/or coding for this available anywhere? Basically we just > need a simple format that communities can localise and run with. Jess Davis is the expert there. Adding her to this bug. Jess, can you let Brian know?
I sync'ed up with Brian and sending teams HTML emails to send from their clients to their lists isn't something we want to get into the business of doing (it can appear spammy and cause some email reputation issues). It's another thing if we want to email them directly the HTML email from ET, and they forward on the information to their lists. Thanks!
Thanks, Jess. So what does that mean for this bug? Also, what's ET?
Exact Target (email client like Mail Chimp).
Thanks, Mardi. I still want to make sure I understand next steps here. Anything you need, copy wise?
You need to log in before you can comment on or make changes to this bug.