Websites/Mozilla.org/One Mozilla/Documentation/Blog-Guidelines/Content-Leads

About Content Leads - DRAFT PLAN * still in progress *

Every team who runs a multi-author, Mozilla-hosted blog appoints a Content Lead. The Content Lead is accountable for the content that is published on the team’s blog. It is up to the Content Lead to decide whether or not a draft blog post needs to be reviewed by or flagged with the PR team. Any posts needing review should be provided in draft form to the PR team three days ahead of time (*more on review timings below*). Key stakeholders should also be involved in the approval process for announcements that shape our strategy. A list of key stakeholders for each product area can be found below.

Overview of Content Leads

Team Name	Blog URL	Content Lead
Your Team Here	Blog URL here	Content Lead Name & Email Here (feel free to update for your blog)
Mozilla Main Blog	blog.mozilla.com	Mozilla Communications Team
Mozilla Privacy	blog.mozilla.com/privacy	Alex Fowler
Firefox Add-ons	blog.mozilla.com/addons	Justin Scott "Fligtar"
Mozilla Security	blog.mozilla.com/security	Dan Veditz and Richard Barnes
Future of Firefox	blog.mozilla.com/futureoffirefox	Laura Mesa / Grace Jimenez
Firefox Metrics	blog.mozilla.com/metrics	Gil Fitzgerald
Mozilla Beyond the Code	blog.mozilla.com/beyond-the-code	Tristan Nitot
Market Insights	blog.mozilla.com/market-insights	Irina Sandu
User Research (to be merged with UX)	blog.mozilla.com/userresearch	Diane Loviglio
L10N	blog.mozilla.com/l10n	Jeff B.
Apps	blog.mozilla.com/apps	Scott DeVaney
Research	blog.mozilla.com/research	DHerman

Product Stakeholders

Product	Stakeholder
Firefox Desktop	(to be added)
Firefox Mobile	(to be added)
Add-ons	(to be added)
Boot to Gecko	(to be added)
Marketplace	(to be added)
Identity	(to be added)
Privacy	(to be added)
Security	(to be added)
(to be added)	(to be added)
(to be added)	(to be added)
(to be added)	(to be added)

Review timings and time zone-friendly posting

If you would like the PR team to review your blog posts, please send it to communications@mozilla.com at least three days before you plan to publish your post. This will give everyone enough time to discuss, review and do some fine-tuning on your post if you need the PR team’s wordsmithing magic or help with the Mozilla messaging. The PR team can also help you to find a good day and time to publish your post, to make sure we get the press attention we want your blog post to receive. If you would like to flag a finalized blog post with the PR team so that they are aware, please do so one day before you plan to publish.

Time-sensitive content that requires a faster turnaround time can also be reviewed by the PR team on short notice: Feel free to drop by the PR team’s desk directly or send an email, flagging the matter’s urgency with [time sensitive] in the subject line.

For globally relevant announcements, keep in mind that Europe (and thus half of the PR team, six PR agencies, and a significant base of journalists and users) is 9 hours ahead of Pacific Time. If you are based on the West Coast, this means that the best time to post something is early Pacific Time, ideally between 6 and 8 am, if not earlier. Everything posted later than that will cause us to lose the opportunity to be part of the day’s news cycle in Europe, or to do any active press outreach at all.

Friday is not a good day for announcements at all, as the EU press team will not be able to do outreach until the following Monday.

Best days for posting news and announcements are Tuesdays and Wednesdays. Mondays (journalists need to clear their inboxes from a lot of news and press releases) and Thursdays (press queries from Europe will have to be turned around on a Friday which is difficult on both sides, journalists and spokespeople) are still okay, but not the first choice to do global press outreach.