Mithrandir, carnuke, All...
The problem lies much deeper to my opinion:
The fact that you return the subject to be a module issue is the wrong thing in all this.
Being a web project manager for since 1996 tought me a few things, one of them is not to treat a project in the eyes of functionality.
A few thoughts/points about it all - CMS is all about managing content!
- Content is being managed by subject, not by functionality (modules).
- Only us (webmasters, projects managers, web developers etc'...) worship the technology behind the content, the end user + the customers (if it's a commercial site) looks at the content and on the way it's managed, as the goal.
- XOOPS (though it's an amasing system), basic concept is functionality and not "by subject" and it won't be changes even with modules like AMS / WFsections / soapbox nad so..
- As one that need/use cms's for 9 years now, I see the need (almost always) as this:
--
subjuct one- articles
- news
- photos (gallery or so..)
- forum
- all others
--
subjuct two- articles
- news
- photos (gallery or so..)
- forum
- all other.......
"System-wide-category" or things like that, lies in the core, not in the module level and might be a thing to think of when going to the next version of XOOPS ....
one more thing is keeping the system (and the modules with it) more orgenised (ie: link images at the images sub dir ... soapbox images @ images/soapbox ... and so on ....)
Don't get me wrong, XOOPS is the best of it's kind and I saw them all, but it lakes a few things that can make it close to perfect
and is "something to think of" ...