Does LiveWhale support a managed workflow for changes to web content?
Not to the extent that some other solutions do.
We know that many commercial CMSs offer the ability to create highly specified workflow processes for different types of managed content; the fact is, workflow is probably the primary area where LiveWhale’s feature set is smaller than that of a typical CMS. Our experience (and our intuition) tell us that the more workflow rigor is built into an automated process, the less individual accountability users feel for the content they manage. So within the pages managed by a LiveWhale group, that group’s regular users have final say over everything that goes live.
One of the primary points of our CMS philosophy is that content management should be done by human beings, not Web applications— the job of the CMS is to make changes easy, and enable the sharing and reuse of content, and not to enforce workflow processes that ought to be working in the real world. In a nutshell, good content management depends on good human communication, no matter how full-featured the CMS is.
There are certainly some workflow models built into LiveWhale. Although groups have full responsibility for managing their own content, notifications of changes and updates are constantly communicated to system administrators, who have the ability to roll any page or dynamic content change back to a previous version or delete it. And calendar events can be submitted by public users (usually after an authentication process for students, faculty and staff) without entering the LiveWhale system.