At LCA2006 I saw a presentation on Plone by an HP staffer (concentrating on its use as a collab tool and knowledge-base for internal teams), which encouraged me to review the state of such things.
Spent a bit of time yesterday and today researching and decided:
* Plone is the way to proceed
* If the Big Boys can live with its database being ZopeDB (no option for MySQL or MSSQL) then so can I
* No it's not PHP or Perl, but Python is cool too
The others I considered were Drupal and Mambo/Joomla.
Plone has a few 'cons': (1) - Unusual Zope/ZopeDB underpinnings and (2) - Steeper learng curve. Also not as easy to 'skin'. The 'pros' were (1) - SMB & NTLM Authentication, (2)Workflow engine, (3) - WebDAV support - along with positive comments on its scalability, and flexability. Overall my impression is that it seems to have more potential as a 'solution for all situations'.
Having said all that, it seems to be a bitch to install on Debian - I failed so far. Simple-pimple install to W32 tho, so I'm evaluating/learning it there for now (running on my work desktop).
Spent a bit of time yesterday and today researching and decided:
* Plone is the way to proceed
* If the Big Boys can live with its database being ZopeDB (no option for MySQL or MSSQL) then so can I
* No it's not PHP or Perl, but Python is cool too
The others I considered were Drupal and Mambo/Joomla.
Plone has a few 'cons': (1) - Unusual Zope/ZopeDB underpinnings and (2) - Steeper learng curve. Also not as easy to 'skin'. The 'pros' were (1) - SMB & NTLM Authentication, (2)Workflow engine, (3) - WebDAV support - along with positive comments on its scalability, and flexability. Overall my impression is that it seems to have more potential as a 'solution for all situations'.
Having said all that, it seems to be a bitch to install on Debian - I failed so far. Simple-pimple install to W32 tho, so I'm evaluating/learning it there for now (running on my work desktop).