Mozilla.com/CMS Requirements

Folks from Mozilla Europe will gather their experience on running a CMS for multiple language sites here to create a set of requirements for something to be used for mozilla.com.

If you have comments, feel free to add them either here or on the talk page (preferred). If a particular topic warrants a detailed discussion, you may want to open a new page for that.

The requirements can be categorized as follows

Content management

• visual identity separated from content
• markup needs to be specified (support validation?)
• localized buttons, localized screenshots
• exposure of raw content
• language selection
• UTF-8 encoding
• English fallback content?

Change management

• staging, approval
• maybe create mandatory and non-mandatory changes, where lack of mandatory changes triggers fallback content

This needs to be further refined, but the change management should expose which locales have caught up with which changes, multiple edits/commits need to be contractable to a single change

Account management

• user roles
  • who can create accounts
  • where are accounts valid (restricted per locale?)
  • who can access staging area
• management of locales
  • adding new locales, removing/deprecating old ones

Editing workflow

The lesson we learned is, not everybody is fond of online editors, not everybody is fond of command line source code management. Thus the CMS should support both.

• expose content to
  • external editors
  • online editor