9
A good observation. XOOPS really isn't a CMS in the sense of managing content on a site. You might use WF-Sections or TinyD or some other module to do that. XOOPS is a framework within which to build applications that make use of the good security, groups, permissions, themes, etc, systems that XOOPS provides.
Mambo is definitely good at handling publishing workflow out of the box.
We have clients that need to do both. We have a XOOPS module on the drawing board that will provide traditional CMS workflow controls for static content that resides inside XOOPS, and probably also for static content that resides outside XOOPS on another website hosted in the same domain.
Essentially, you would use XOOPS as your private, internal website for knowledge sharing and collaboration, and XOOPS would also be the control panel for managing the content in your public website.
Sound cool? Don't get too excited, it's still vapourware, and we have no idea whether it would be released publically, and whether it would be GPL'd even if it were released.
If others know of full publishing workflow management modules for XOOPS, I'd love to hear about it. But so far I have uncovered none.
--Julian
P.S. Mithy, a horizontal block option would ROCK.
