Forum Moderators: phranque
Portals/CMS:
Drupal: [drupal.org...]
Geeklog: [geeklog.net...]
Mambo Open Source: [mamboserver.com...]
PHP-Nuke: [phpnuke.org...]
phpWebSite: [phpwebsite.appstate.edu...]
Post-Nuke: [postnuke.com...]
Siteframe: [siteframe.org...]
Xoops: [xoops.org...]
They are all very popular ones, I have yet to hear very negative things about any one in particular but phpNuke (which I think is due to the fact that they are the most popular, not becasue they are that bad)
HTH :D
I came up with these features that I consider a must have:
1) Templates beyond the PhpNuke-style approach à la 'you can choose what the
blocks look like.' This will weed out most of the PHPNuke clones.
2) Caching of result pages.
3) Permission system.
4) Managing of multilingual content.
4) Easy to learn.
4) Good documentation.
5) Straight-forward, clean and modular achitecture. This is a trait most PHP-
based solutions do not posess because PHP didn't have many of the higher level
programming constructs in the beginning.
6) News with teasers on home page.
Also I would like to hear what webmasters think about the CMS they are using right now.
It's very cool, and looks to have all of the features you've described. Plus, you've got the Zope backend, so it's very easily extensible.
Anyway, the Zope/CMF/Plone triad looks best to me so far. It's mature and has a clean architecture. Plone is a layer on top of CMF (content management framework) which is a layer on top of Zope which is implemented in Python. I always wanted to learn Python, so this is a good chance to do so. Zope's ZPT is the most clever way of introducing dynamicity into HTML I've seen so far! Compared to, say JSP, PHP, Perl's HTML::Template and SSI; that is.