> > I picture a web-based frontend as well as a web-based backend. > > Cocoon powers the backend just like it powers the frondend: serving the > pages. > > Sure, you might not need the 'full' cocoon potentials on the back end > (but to provide previews or completely WYSIWYG inline-editing, you do!) > but I see the backend as an-editing oriented web(dav?) application on > top of Cocoon. > > (yes, it's piece of cacke to add WebDAV functionality to Cocoon > directly, it's just a bunch of new HTTP actions and some XML content, > not a big deal for our machinery)
And, the backend can be written as cocoon-based app, mozilla-based app, java app, Cocoa app or even Win32 MFC app! I see that the backend is mainly used by content producers: they are producer, editor and designer. Each of them has a specific role. For example, editor writes the whole or partial content, the designer provides graphics and style for the presentation, and the producer merges the content from various editors, reject some of them, prove-read and assign style for the final presentation. Hence, the backend system must present such logic for this kind of workflow. But which one provides workflow? Of course, it is the CMS. Hence, the backend provides "frontend" to the content producers, while frontend provides presentation to content consumers (viewers). A clear picture now. > > Also, consider things like having editors down in Afganistan feeding > their news via Palm connected to satellite cell-phones (UTMS anyone?), > having their directors approuve the news while they are on an airplane, > with the ability to annotate things directly on the page and without > requiring any specific software to be installed on either client. > > See the need for cocoon on the backend? :) I see, not only cocoon, but more!! > > -- > Stefano Mazzocchi One must still have chaos in oneself to be > able to give birth to a dancing star. > <[EMAIL PROTECTED]> Friedrich Nietzsche - Punky > -------------------------------------------------------------------- > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
