-
Revision 281 by kore at Tue, 11 Sep 2007 09:02:21 +0200
-
Revision 231 by kore at Fri, 17 Aug 2007 13:44:25 +0200
-
Revision 229 by kore at Fri, 17 Aug 2007 13:39:32 +0200
-
Revision 106 by kore at Sat, 28 Jul 2007 12:48:04 +0200
WCV - Description
The name
WCV means web content viewer, which indicates, that this is no Content Management System, but just a content viewer. The next paragraph and the design document describe this in further detail.
What does it do?
WCV uses a very extendable handler mechanism to display content managed in directory structures with some version control system or from nearly any other sources (CMS, ...).
The basic idea of just displaying directory contents, with some index definitions, as a website - and using the filesystem to structure the content, with all its features like links, collections and file types - bases on a small proof of concept by Tobias Struckmeier - thanks for the idea.
WCV enriches this idea with metadata fetched from various sources, and also allowing virtual directory trees, if this makes sense. An example for virtual trees may be structuring blog articles into categories - even this may also be done with symlinks. This also enables you to integrate subtrees completely fetched from some CMS data storage.
Using a user extendable handler mechanism, the directories, files, content and meta data may be handled and fetched separately and displayed with different display decorators for different output, like HTML, text, PDF or the original binary.
Mainly used for static cached content, also dynamic user interaction is possible when the content classes are implementing the corresponding interfaces. Any content nodes may define themselves as dynamic, so that the engine won't cache anything.
License
WCV is licensed under GPLv3.