Websites/Mozilla.org/One Mozilla/Documentation/Blog-Guidelines/Content-Leads: Difference between revisions

Websites/Mozilla.org/One Mozilla/Documentation/Blog-Guidelines/Content-Leads (view source)

Revision as of 17:03, 16 March 2012

35 bytes added , 16 March 2012

→‎About Content Leads

Vponell

28

edits

Revision as of 16:41, 16 March 2012 (view source) Vponell (talk \| contribs) No edit summary ← Older edit		Revision as of 17:03, 16 March 2012 (view source) Vponell (talk \| contribs) (→‎About Content Leads) Newer edit →
Line 1:		Line 1:
	=About 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.		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.