History for ZopeInCommercialWorld

??changed:
-
    
    <a href="http://www.zope.org/Resources/CaseStudies">Case Studies for ZOPE</a> is a good reference, obviously :)

    **runyaga**
       
       Here is my experience:  We used a very modified form of the Portal Toolkit, so that members (employees) could
login and edit content that was appropriate to their "grouping".  It had very basic workflow (using the ZCatalog and attributes of the content)
so that editors could proof the content and then approve it.  After approval it would then be 'shipped' out in XML to the webservers, notify the
servlets of an update and then be transformed into html to be included at next page request.  **Works great!**

       The biggest obstacle, in my company was of political nature and 'partnerships'.  We now use Teamsite (written in Perl) on our larger
projects, strictly because of our relationship to Interwoven.  Technically, I would say it usually takes longer to implement 
a Teamsite solution than it would with a ZOPE custom solution.  Expense-wise Teamsite is much more expensive - to do most of the things ZOPE
does out-of-the-box costs ~$70k.  I hope to write a Comparison of Teamsite and ZOPE after my project ends.  If you have a group of 
programmers who know neither, Teamsite or ZOPE.  And you have limited funds (all should go into sink redundancy of hardware :) - ZOPE seems
to me the more enjoyable to program on the two platforms.  Also there is a significant community built around ZOPE - Teamsite is based strictly
around consulting, so its very close-sourced and tight-lipped.