Hi, I am more of programmer than designer. and thats
my experience of my two sites of XOOPS for communities of about 300 peoples (10% really active - submitters):
XOOPS is my first CMS to live with.
* Fluent instalation
* quite intuitive admin panel (backend) - thoug sometimes was time consuming to deal with access rights..
* smarty wasn't of big (or maybe even any) use for me..
* was time-consuming to find and make up the design we wanted
* I managed to hack some modules, but didn't manage to make up my own (even a blank one..).
** because there were not enough docs
** for me XOOPS OO seemed compicated to code according to it
* was hard time (well, more of "took a while") making up horizontal dynamic menus
* my XOOPS theme loads slower than mambo sites I know (well may be I overloaded it with js.. - for dynamic menu and and ability for modules to collapse
http://somsa.ktusa.lt/xoops)
MAMBO is what I used now for several projects.
* installation no worse than XOOPS (even has sample data - to see the basic design of site at once)
* theming/designing is more simple (HTML with some php)- so time-saving (we all like it, don't we :) - bigger variety than XOOPS
* can have unlimited areas for blocks (xoops has just 5: R, CC, CR, CL, L).
*
Has good content management in the core (xoops has probably 5 content management modules, and its confusing..)
* a bunch of adopted dynamic menus and WYSIWYG editors
* navbar/pathway in the core*
more flexible, because
** mambo is more modular (imho) - it lets develop and manage blocks separately from modules (in mambo terms blocks are called "modules" and modules are called "components" - strange ;).
** mambots - things for linking between modules(components in mamb) - didn't try, but they have potential
* user management - groups can inherit rights according to hierarchy - so easier to setup installed features (especially, when there are many features)
* seems to have bigger community
=> generally - more
admin-friendly and user-atractive, and users are the reason, why we need Portal systems, isn't it?
* and multilanguage (still a hack, but promises to be in the core of v4.6 (now is v4.5.1)) (also multiple categories for articles promised in 4.6)
several minuses:
- at first it seems weird, that components and modules are stored separately
- doesn't have comments feature in core, but there is mambot whitch can help ;) (generaly it is orentiered more towards content than community).
- well, they have tey own cache system, don't know about it more
- updates are more often than xoops, but the reason in my mind is that mambo is evolving more dynamically
- v4.5.1 still doesn't have fully integrated gallery. but media manager or paralelly installed RC Gallery with random photo block can help
may be I wrote not very clearly, so I'll check out if some questions will arise