Content management ecosystem
A Content management ecosystem is a group of content management systems linked together by shared purposes, contributors, and materials. There are a variety of opportunities to research and experiment with related issues, including synchronization, language, format, and communication.
History
(more to come)
The Content Management Ecosystem model originated from the PhD research of OLPC volunteer Todd Kelsey, who at the time of writing has been exploring how various open source content management systems and related tools could be used to help support scalable, accessible and sustainable community websites.
OLPC
As of late Nov of 2007, there is discussion about how OLPC initiatives can be explored through a combination of such systems; and how to make changes in existing communities in the CME transparent across other communities.
Forums
- scripted gateways: mail-to-forum, forum-to-news?, forum-to-wiki
- forum platforms with large userbases : phpbb, et al.
Wikis
Currently, there are a public and team wiki about OLPC, related projects on en:wp, wikieducator, wikibooks/wikijunior, and more.
Identity
The use of tools such as OpenID to unify identity processes among many different sites allows for users to have just one username and confirmation process for many sites.
Languages
Localization and the capacity for same, including Unicode support and font support for rtl languages, is important to maintain cross all platforms.
R+D
Translation Management
(Open Source)
- Pootle: OLPC is using an open source tool called Pootle to help manage the process of translating text used in interfaces and applications on the XO.
(Commercial)
- Idiom: Idiom has donated an instance of their enterprise translation software that is being explored as a basis to help develop a translation memory for OLPC. [http://www.idiominc.com]
- Give access to:
- sj
- cooper.me
- Give access to:
Single Source Authoring
Single Source Authoring is the concept of having an authoring application that can manage content development and output to a variety of formats. The value of SSA in general terms is to enable massive scalability of content such as documentation, where the system can manage updates to an original language version, and then automatically generate requests for translation for other language versions, and then handle the integration of that content back into the original version.
Single Source Authoring can also be thought of as a process and a writing style. Single Sourcing: Building Modular Documentation is a book that deals with this subject in general, and how to write in a modular style in particular.
(Open Source)
- At the present time, due to the complexity of the underlying software, there aren't any mature open source projects that offer true single source authoring. There may be several projects in the works that could be expanded on though, such as Coccoon. (don't know link reference)
(Commercial)
- Author-IT: Author-IT has donated an enterprise instance of Author-IT via CFTW (a non-profit that is supportive of OLPC) to explore how the software could be used to allow rapid release and management of content in a number of languages. [http://www.author-it.com]
Brainstorming
Forum > Knowledgebase
excerpt from email (11-28-07): skype forums > community support forum > there's a little disclaimer (along with a link), asking people to please search the <link>knowledgebase</link> before posting. one option is to use a separate knowledgebase, populated by volunteers. if phpmyfaq ends up being viable, it could be an option -- like feeding people into a searchable unit to help reduce the redundancy of people posting and replying. or perhaps phpbb has a knowledgebase