Difference between revisions of "Documentation/Dashboard/CMS Evaluation"
From Apache OpenOffice Wiki
< Documentation | Dashboard
m (main goal of the intended tool) |
m (minor correction) |
||
| Line 24: | Line 24: | ||
* clearcut content (e.g. "user help & program documentation"), not intermingled with project related stuff (like in the services-wiki) | * clearcut content (e.g. "user help & program documentation"), not intermingled with project related stuff (like in the services-wiki) | ||
|Highest ;-) | |Highest ;-) | ||
| − | |if the intended | + | |if the intended target audience for the tool is the end user (if not, cancel this req!) |
|- | |- | ||
|Enter Requirement here | |Enter Requirement here | ||
Revision as of 14:51, 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!) |
| Enter Requirement here | High/Med/Low | Notes |
Tools to Evaluate
| Tool | Description/URL | Pros | Cons |
|---|---|---|---|
| Plone | CMS built on top of Zope, e.g. http://www.oooauthors.org | ||
| Mediawiki with Extensions |
