First off, thanks to everyone that has replied - really helps. I've received some very good advice re: mapping my data tables to classes, and for better or worse am on the path of encapsulating much of my logic in external methods and pluggable brains. Regarding the suggestions to use CMF: My thoughts are right in line with Oliver's sentiments below: I ruled out CMF and (though it was a lesser consideration anyway) Plone because they contain far more stuff that I DON'T need or want then things that would be of help. I have no interest in wading through the process of learning the CMF during a project schedule just for the utility of the few things I would use. Learning ZPT is much higher on my list, and even that is deferred until I finish the project at hand (again, for better or for worse). Also, this is a functionality-heavy site I am working on, not a content-heavy one. I am using Zope as an application framework in this case rather than as a content management tool. I do wish that various CMF functions were available as individual products - that would be great. Thanks again for the advice, everybody, and keep it coming if there's more!
Sean, I also like the CMF ways esp. for the skins tool, but how do you handle the stuff coming with CMF you _don't_ want to use. Like the membertool, workflows, syndication etc. Do you have a custom CMF-site object, do you delete the autocreated objects you don't like after adding a stock CMF site? Also, how are you handling the fact that now your products now are "not in one piece", since methods are spread through the skins tool? I really wish the CMF wouldn't be effectively one big software BLOB.