718
edits
Websites/Mozilla.org/One Mozilla/Documentation/Blog-Guidelines: Difference between revisions
Websites/Mozilla.org/One Mozilla/Documentation/Blog-Guidelines (view source)
Revision as of 19:13, 6 March 2012
, 6 March 2012→Blog Guidelines - Summary:
| Line 7: | Line 7: | ||
In the past, press, our users and even Mozillians often found it hard to follow what the Mozilla project stands for with regard to different industry developments. The objective of these guidelines is to make the most of the power of so many passionate, knowledgeable voices for the greater good of the open Web, and not to limit the free and open communication which is a hallmark of the Mozilla project. [https://wiki.mozilla.org/One-Mozilla-Project/Documentation/Blog-Guidelines/Why read more . . . .] | In the past, press, our users and even Mozillians often found it hard to follow what the Mozilla project stands for with regard to different industry developments. The objective of these guidelines is to make the most of the power of so many passionate, knowledgeable voices for the greater good of the open Web, and not to limit the free and open communication which is a hallmark of the Mozilla project. [https://wiki.mozilla.org/One-Mozilla-Project/Documentation/Blog-Guidelines/Why read more . . . .] | ||
==Blog Guidelines - Summary | ==Blog Guidelines - Summary== | ||
*Official news, announcements or any important updates will be posted on Mozilla-hosted communications channels first, but can be cross-posted to a personal blog at the same time | *Official news, announcements or any important updates will be posted on Mozilla-hosted communications channels first, but can be cross-posted to a personal blog at the same time | ||
| Line 13: | Line 13: | ||
*Every multi-author blog has a dedicated Content Lead. The Content Lead decides whether or not a blog post has to be flagged or reviewed by the PR team. (*more details on Content Leads below*) | *Every multi-author blog has a dedicated Content Lead. The Content Lead decides whether or not a blog post has to be flagged or reviewed by the PR team. (*more details on Content Leads below*) | ||
*The PR team should review any major announcement before it is posted, and may also support with a communications plan | *The PR team should review any major announcement before it is posted, and may also support with a communications plan | ||
*If you would like to set-up a new Mozilla Blog, please file a bug and the PR and Creative teams will help get you rolling. | *If you would like to set-up a new Mozilla Blog, please file a bug and the PR and Creative teams will help get you rolling. | ||
==What makes a Mozilla Blog== | ==What makes a Mozilla Blog== | ||