718
edits
Websites/Mozilla.org/One Mozilla/Documentation/Blog-Guidelines: Difference between revisions
Jump to navigation
Jump to search
Websites/Mozilla.org/One Mozilla/Documentation/Blog-Guidelines (view source)
Revision as of 19:17, 6 March 2012
, 6 March 2012→Starting a New Mozilla Blog
| Line 36: | Line 36: | ||
'''Step 1.) File a bug for a new blog request''' | '''Step 1.) File a bug for a new blog request''' | ||
* If you would like to start a new blog on the Mozilla infrastructure, please [https://bugzilla.mozilla.org/enter_bug.cgi?product=Websites file a bug here under "blog.mozilla.org"]. | |||
If you would like to start a new blog on the Mozilla infrastructure, please [https://bugzilla.mozilla.org/enter_bug.cgi?product=Websites file a bug here under "blog.mozilla.org"]. | |||
'''Step 2.) Determine a channel''' | '''Step 2.) Determine a channel''' | ||
* The PR team will help you define the appropriate channel, which might be a new blog, a category on an existing blog, etc.) | |||
The PR team will help you define the appropriate channel, which might be a new blog, a category on an existing blog, etc.) | |||
'''Step 3.) Develop Creative Assets''' (if needed) | '''Step 3.) Develop Creative Assets''' (if needed) | ||
* The Creative team will help develop any visual assets and identify the right platform to reach your target audience (developers, users, contributors, etc). | |||
The Creative team will help develop any visual assets and identify the right platform to reach your target audience (developers, users, contributors, etc). | |||
'''Step 4.) Appoint a content lead''' | '''Step 4.) Appoint a content lead''' | ||
* Every team who runs a multi-author, Mozilla-hosted blog should appoint a [https://wiki.mozilla.org/One-Mozilla-Project/Documentation/Blog-Guidelines/Content-Leads Content Lead]. 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. More on Content Leads can be found [https://wiki.mozilla.org/One-Mozilla-Project/Documentation/Blog-Guidelines/Content-Leads here.] | |||
Every team who runs a multi-author, Mozilla-hosted blog should appoint a [https://wiki.mozilla.org/One-Mozilla-Project/Documentation/Blog-Guidelines/Content-Leads Content Lead]. 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. More on Content Leads can be found [https://wiki.mozilla.org/One-Mozilla-Project/Documentation/Blog-Guidelines/Content-Leads here.] | |||
==General Communications Guidelines== | ==General Communications Guidelines== | ||