MDN/Archives/Kuma/Features/EditorialTools: Difference between revisions

From MozillaWiki
< MDN‎ | Archives‎ | Kuma
Jump to navigation Jump to search
No edit summary
No edit summary
Line 7: Line 7:
|-
|-
<section begin="status" />
<section begin="status" />
| Editorial Tools
| '''Editorial tools'''
| {{StatusHealthy|status=In planning phase}}
| {{StatusHealthy|status=Planning}}
| -
| -
| -
| -
Line 17: Line 17:
== Summary ==
== Summary ==


Provide tools for more formally managing content created on the MDN website.
Tools for more formally managing content created on the MDN site.


== Release Requirements ==
== Release Requirements ==
Line 28: Line 28:


* Review and approval work flow
* Review and approval work flow
** RSS feeds for docs that need attention
* Word / paragraph / character counts for all articles
** Documents needing review should be presented to users with necessary permissions and tags for that area of expertise
* Doc versioning and tagging for releases, vendors, versions, etc.
** Ping potential reviewers if article has not been looked at for a while
* A status for each article
* Document versioning and tagging for releases, vendors, versions, etc
** Draft, Needs technical review, Needs editorial review
* RSS feeds for docs that changes states (draft to review, review to published, etc)
** Ideally, this list should be customizable
* Word/paragraph/character counts for articles
* An article marked as needing technical review should be presented to users who have indicated that they are experts in that topic and who have the necessary permissions to make changes to that article
* Notify potential reviewers if an article has not been reviewed for a while
* RSS feeds
** Docs that need attention
*** Docs needing technical review
*** Docs needing editorial review
** Docs that change states (draft to review, review to published, published to draft, etc.)


== Risks ==
== Risks ==

Revision as of 17:41, 26 May 2011

Feature Status ETA Owner
Editorial tools Planning - -

Summary

Tools for more formally managing content created on the MDN site.

Release Requirements

-

Next Steps & Open Issues

-

Related Bugs & Dependencies

  • Review and approval work flow
  • Word / paragraph / character counts for all articles
  • Doc versioning and tagging for releases, vendors, versions, etc.
  • A status for each article
    • Draft, Needs technical review, Needs editorial review
    • Ideally, this list should be customizable
  • An article marked as needing technical review should be presented to users who have indicated that they are experts in that topic and who have the necessary permissions to make changes to that article
  • Notify potential reviewers if an article has not been reviewed for a while
  • RSS feeds
    • Docs that need attention
      • Docs needing technical review
      • Docs needing editorial review
    • Docs that change states (draft to review, review to published, published to draft, etc.)

Risks

-

Use Cases

-

Designs

-

Test Plans

-