I'm researching OS CMS options for a project, and while XOOPS seems like a very robust system, I've encountered a couple of feature questions. After reviewing the documentation, I cannot find answers. Can anyone help me with the following questions (or provide links to relevant resources)?

1. Does XOOPS allow workflow management? I know this is a pretty sophisticated requirement, but I am looking for a module/plugin that allows me to define content workflow states (private, submitted, published, etc.), define workflow roles (content creator, editor, etc.), define content actions (view, create, edit, publish), assign users to roles, and restrict user actions based on role/state combinations.

2. Does XOOPS allow easy content type creation? I know there are useful standard content types like Web pages and news items, but my project requires the creation of new content types. I'd like to be able to quickly create new content types and have them be fully integrated with the CMS, where all of the admin tools are available, they appear in the permissions options lists, etc.

As far as I can tell, Plone is the only OS CMS that offers these features, but I'd like to stick to a LAMP solution, and XOOPS seems like a great option.

Thanks for your help,
Chris

I've actually used Plone for perhaps 2 years now (as a producer/pm), and am strongly considering a transition to XOOPS.

In response to your questions, Plone runs on python, with pages built via a special markup called TAL, so there might be some new languages for you to learn. I think Plone is also a lot more feature-rich and generic, making the learning curve a lot steeper. Like XOOPS it has a strong developer community with active newsgroups and some Plone-specific books published (if you're really interested, I've been hearing good things about Andy McKay's recent Plone book).

As far as I can tell, XOOPS does not support easy content type generation or workflow controls (both are standard in Plone) - can anyone verify?

Thanks
Chris