Difference between revisions of "Documentation/Dashboard/CMS Evaluation"
From Apache OpenOffice Wiki
< Documentation | Dashboard
(→Requirements) |
(→Requirements) |
||
| Line 26: | Line 26: | ||
|if the intended target audience for the tool is the end user (if not, cancel this req!) | |if the intended target audience for the tool is the end user (if not, cancel this req!) | ||
|- | |- | ||
| − | |'''Easy | + | |'''Easy translation process:''' with one mouseclick to template for translation <br />The translation is reached by a flag-language-changer. |
|Very high | |Very high | ||
| | | | ||
Revision as of 19:54, 21 January 2008
CMS Evaluation for Multilingual Documentation Maintenance
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.
Requirements
Enter requirements that a content management framework should meet. Think problem, not solution.
| Requirement | Priority | Notes |
|---|---|---|
Usability: ease of use and unambiguousness for end users
|
Highest ;-) | if the intended target audience for the tool is the end user (if not, cancel this req!) |
| Easy translation process: with one mouseclick to template for translation The translation is reached by a flag-language-changer. |
Very high | |
| Different documentation formats: Different mimetypes are allowed to up- and download. ODF-Files and PDF-Files are displayed inside the framework without converting. |
Very high ;-) | See and read online, what you could get :-) |
| Management of rights: Different areas of documentation types: from lower proof of quality to high proof (with workflow). Management of rights for every object inside the framework (directory, file etc.) |
Very high ;-) | Like in OOoAuthors we also need documentation with high quality ;-) |
Tools to Evaluate
| Tool | Description/URL | Pros | Cons |
|---|---|---|---|
| Plone | CMS built on top of Zope, e.g. http://www.oooauthors.org | ||
| Mediawiki with Extensions |
