* Perrin Harkins ([EMAIL PROTECTED]) [011017 10:40]: > The problem is, no two people on earth agree about what a "content > management" system is. Some people think it's the ability to edit > web pages through a browser text field. Others think its version > control. Still others think it's workflow and templating for data. > As you've discovered though, about 99% of the open source world > thinks 'Content Management System' eq 'Slashdot'.
File this along with 'Knowledge Management'... > Building a useful system would be fun. I've considered building > something to handle static files by hooking up mod_perl with CVS and > providing a web GUI for basic site workflow. I've also considered > building a system that provides workflow, scheduling, and versioning > for user-defined data objects, probably using OpenInteract. The > trouble is, with so little agreement about goals and requirements, > it's hard to get started without an actual project that needs it. This is somewhat OT, but I've had in the back of my mind the ability to create object versioning for SPOPS. This actually wouldn't be that difficult -- every time an object is successfully saved, the system would submit the old version to an engine that could either do it with a database (find the last version, create an entry for the new version and enter along with it any notes from the user) or with a filesystem.... Too much fun stuff to do! Chris -- Chris Winters ([EMAIL PROTECTED]) Building enterprise-capable snack solutions since 1988.
