accessible content management system
Maintainer: Tomas Cerha <cerha@brailcom.org>
Index:
Quick links:
Wiking is an open source content management system. You can manage your web-site using a web browser.
Primary design goals:
Key features:
The concept of content creation using "structured text" (generalized markup derived from the well-known wiki formatting) proved to be well usable for people without technical background. Also, together with an accessible user interface, this makes Wiking a suitable content management tool for blind people or people with other handicaps.
Wiking is written in Python and is based on two other important components:
In fact, Wiking is nothing else than a web interface to the Pytis toolkit and an application built on top of this toolkit. The actual CMS logic resides in modules and the engine itself is very tiny piece of code. This makes the system easily extensible and maintainable.
The current implementation runs on Apache web server (over mod_python) and stores its data in the PostgreSQL database. In theory, these components could be replaced, however.
The first prototype of Wiking was released sometimes in late 2003. It was written in Perl and it served as a platform for experimenting with web content accessibility and design of a user interface which is intuitive, remains visually attractive and provides all the features one expects from a “typical” web portal. The CMS itself was intentionally kept very simplistic since it was still considered a prototype, but many important features, such as multilingual support or two-phase publication process were already included. It evolved slowly for about three years and ended up in June 2006 with the version number 0.3.12. The 0.3.x version will be maintained, but no new features will be added.
The development of a new version written in Python began in June 2006 and the primary reason was the challenge to use the LCG to provide an accessible web interface to the Pytis toolkit.
You can manage multiple language variants of your content and Wiking defines the logic needed for serving it. This is done using the Content Negotiation technique and the user is also able to override the language preferences configured in the browser by choosing a language manually.
Wiking user interface is currently translated into the following languages:
The translations marked as partial include all messages needed for serving the content, but don't include translations for the management interface.
Adding support for other languages is very simple (using the GNU gettext framework) and we welcome anyone willing to contribute translations. Please contact the project maintainer or the mailing list for instructions.
Check the following sites to see Wiking in action:
The sites below are using the older (0.3) version:
Full documentation is available as a part of the project and is distributed together with the source code.
if "/doc/wiking" ?>You can browse the HTML version on-line.
/if ?>Latest released version is 0.4.2.
The source code is managed using CVS. There are the following options to get the current development version.
Anonymous CVS access (login with an empty password):
cvs -d :pserver:anonymous@cvs.freebsoft.org:/var/lib/cvs login cvs -d :pserver:anonymous@cvs.freebsoft.org:/var/lib/cvs checkout wiking
Subscribe to the mailing-list wiking-cvs@lists.freebsoft.org for notifications about all CVS commits.
The CVS module for the old Wiking version (0.3.x) written in Perl is wiking_old and here is its www interface.
There is a public mailing-list wiking@lists.freebsoft.org for this project.
This list is for for Wiking developers, as well as for users. If you want to contribute the development, propose a new feature, get help or just be informed about the latest news, don't hesitate to subscribe. The communication on this list is held in English.
See also the listing of all Free(b)soft mailing lists.