4
jegelstaff: Thanks, great link. However I completely disagree. To purposely limit flexibility of implementation and design because certain people think it's ugly is short-sighted. From my experience some of the most interesting and refreshing things happen when technology is used and abused. And why should technological limitations dictate "good" design and style? Sharing source and technology is about freedom right? If people want to do crazy stuff let them hang themselves. It often stimulates and pushes innovation.
I whole-heartedly apologize for my comments regarding Mambo not really having really immersed myself in it yet. But it seems that most people don't really disagree that Mambo is a content-management system with more flexibility of layout and content types whereas XOOPs is a community driven site with the future posibility for modular addons that would make is behave more like a CMS, i.e. staging, revision, granular editing process.
To clarify I should say I wish the limitation of XOOPS to 5 blocks would not take it out of the running for certain projects. As far as code implementation I can't say but for many projects the flexibility of design far out-weighs the need for hundreds of free modules. I'm recklessly sticking my neck out here but my guess is that most sites, XOOPS sites included, don't use more than a small handful of the modules common to all CMSes and portal software. If most sites need these basic modules and one has more flexible templating I'd say XOOPS might not nessarily be the best choice. That said I do like what I've seen of XOOPS so far so I'll probably take the time to experiment with it.