Website CMS:Requirements: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 34: Line 34:
* RSS feeds of
* RSS feeds of
** Changes to pages when a writer requests review from a leader
** Changes to pages when a writer requests review from a leader
** Per language feed of content changes
** '''others?'''
** '''others?'''



Revision as of 10:38, 5 December 2006

Website CMS

Requirements

I don't expect this to be perfect before we begin, just to serve as a guideline so we're all on the same page. Please ask questions.

I've prefixed requirements with (?) if I'm not sure it should be a requirement or not. Edit as appropriate. :) Please distinguish "must have" and "nice to have" features.

Outstanding Questions

  • how does the review process work? ie. what is the workflow from a writer modifying a page to it going live?

Content Creation

  • Directories and html files can be created through a form
  • (?) Other file types are uploadable through a web form
  • Content creation is not restricted to language (requirement created from current system)

Content Management

  • Static and dynamic content can be modified as plain text in textareas.
    • (?) Dynamic content only (verify this?) can be modified with wiki markup

NOTE : JsToolbar allows wiki/wysiwyg editing and produces xhtml code, plus it has a dynamic xhtml source editing to add more complex markup.

  • All changes to static content will be tracked and archived.
  • (?) An easy way to view and revert to older versions of static content.
  • (?) An easy way to compare what changed between two versions of static content.
  • Input will be accepted in any language currently used on mozilla.com.

Presentation / Publishing

  • Multiple pages for a single language can be published with one click
  • Administrators can push an entire language live with one click
  • RSS feeds of
    • Changes to pages when a writer requests review from a leader
    • Per language feed of content changes
    • others?

Administrative Process

  • A user can be in one of two groups:
    • Writers (can edit static and dynamic content) (approx 40-80 people)
      • proofreaders are in this group
      • Can edit any static or dynamic content
      • Requests to go live go to a leader for review
    • Leader
      • Can edit any content, but can also request a push live
    • Administrators (approx 5 people)
      • Can push changes live
      • Can email all active members through a single form
  • Users can be added to the system by administrators
  • Users can be disabled
  • Users will have their own usernames and passwords to login
  • Simplified front end for Bugzilla (similar to IT requests (would require integration with bugzilla japan)