Archive:CMS solution for Fedora Project websites

Scope requirements for a potential usage of a CMS underneath specific content delivery sites; owner quaid

Target (sub-)domains and paths

• http://fedoraproject.org*, non-wiki content:
  • https://fedoraproject.org/en/get-fedora
  • https://fedoraproject.org/en/join-fedora
  • https://fedoraproject.org/en/get-help
  • http://fedoraproject.org/wiki/Legal (to move out of the wiki)
  • http://fedoraproject.org/wiki/Licensing (to move out of the wiki)
  • http://fedoraproject.org/wiki/Packaging/Guidelines* (to move just the guideline pages out of the wiki)
• http://docs.fedoraproject.org*

Time frame/schedule

1. Scope need, vet solutions -- mid Sep.
2. Bring up docs.fp.o -- early Oct.
3. Tweak through F10 release
4. After F10, migrate www. to tweaked solution

Solution requirements

Must

• Good security record
• Proactive security mindedness of developer community
• Highly responsive, especially to security issues
• Flexible enough auth system to attach to FAS
• RSS
• l10n that doesn't break the translator workflow
  • Output for Transifex (PO/POT)
• Content workflow (write <=> edit => publish)
• Internal version control with rollback capability
• Content expiration (automatic)
• Multiple roles, e.g. writer, team lead, editor, publisher, managing editor
• Categorize/tag content for easy base organization
• Search that works
• Integrate with FAS
• Be a CMS as a core function, not an add-on
• Handle making certain pages or content areas static/non-database driven, such as for scaling during times of heavy resource demand

Should

• Do OpenID
• Have a good WYSIWYG editor
• Be easy to organize content by taxonomy, structured and ad hoc
• Support for draft->review->$foo->publish workflows
• Be able to ship the content for l10n only at certain stages
• Have the workflow go back to a certain stage if a mistake/error is found in the source-language content by the translator
• Translators have a 'review' step in the workflow for translated content before it is published, so that they can see translations in context
• Be written on modern technology with a vibrant community and likelihood of being popular beyond the next twelve months.
• Have good federation tools to make it easy to find disparate content through one UI
• Not try to be all things but for the things we need, do it right

Other good qualities

• Be a modular design (v. monolithic)
• Have an active and large community
• Have support for DocBook