Difference between revisions of "Documentation/Dashboard/CMS Evaluation"
|Line 17:||Line 17:|
Revision as of 11:16, 14 March 2008
This page is intended to collect and discuss requirements, processes, and tools to implement a content management framework that allows maintenance of multilingual documentation.
The goal is to find a way to intelligently create, update, localize, and publish documentation in multiple languages. We are in agreement, that the current Mediawiki-based solution, while having unbeatably low barrier to contribution, lacks basic content management functions required to maintain documentation in multiple languages, and publish documentation that went through review and quality assurance cycles.
Will the CMS also be used as publication platform for users?
Walter is a professional technical writer and would like to devote some of his time and contribute to the OOo documentation. He can do authoring and editing. He is new to CMSs and usually works with Framemaker.
Sheila is an advanced OOo user, a native English speaker, and willing to help out on OOo docs.
Jane is a free-lance author who writes books about OOo and publishes them. She would like to make content available to the community without jeopardizing her ability to earn money with her books.
Francois is a beginner OOo user, a ntive French speaker and would like to maintain some French documents.
Enter requirements that a content management framework should meet. Think problem, not solution.
|Access Control||Availability of customizable user group access levels, document based, document-type based, or document-status based|
|Multi-Language Access||GUI must be available in multiple languages, swithcing between document languages|
|Localization||Allow for localization of documents, availability of glossary, terminology, translation memory, or interface to external localization tools and formats|
|Document Workflow||Document creation and maintenance must take place inside a customizable work flow including steps to create, edit, review, publish, and archive documents in multiple languages|
|Document Publication||Ability to publish documents internally and to different sites in different formats (ODF, PDF, HTML)|
|Extensability||Framework to add extensions that provide special services, availability of vibrant extension development community|
|API for programmatic access||Ability to automate tasks like mass-changes to documents using API access|
|Metrics||Ability to measure access and usage metrics|
|ODF support||Support of ODF documents, metadata evaluation, search in ODF, ODF diffs, plugging of OOo instances|
|WYSIWYG support||Support of WYSIWYG editor for non-ODF content|
|Document Versioning||Version control of documents, ability to recover/rollback old versions, milestones, creating release tags across different documents/languages|
|Document Rating||Rating of documents by readers (only required if CMS will also be the publication framework)|
|Comments||Add comments to documents by readers (only required if CMS will also be the publication framework)|
|Ease of Use|
Tools to Evaluate
See also the Wikipedia list of CMSs
|Plone||CMS built on top of Zope, e.g. http://www.oooauthors.org, http://www.plone.org||
|Mediawiki with Extensions||
|Drupal||Very popular CMS||
|Alfresco||Alfresco is the Open Source Alternative for Enterprise Content Management (ECM), providing Document Management, Collaboration, Records Management, Knowledge Management, Web Content Management and Imaging.||