You can use Plone for lower-budget sites, but it is not the optimal use for Plone. The sweet spot for Plone is probably is for those $50K+ projects. You can get Drupal hosting for cheap ($10/m?) whereas Plone hosting is going to start at $50/m. If you are doing off-the-shelf CMS deployments though you would mostly be concerned with "Plone the CMS" vs. "Drupal the CMS". I read a good comparison between the two here the other day:
http://m.odul.us/2007/09/02/plone-vs-drupal-take-one If you are interested in sharing Python code between TG and Plone though, then there is a new project just for that called Repoze: http://repoze.org This is really where the future of Python web development is very exciting right now, at least for people building more complex sites. For example, lets say you have a site that has: * Standard CMS needs * Custom application needs You might take an off-the-shelf Plone, do some stock customizations in the Plone Site Setup control panels, maybe build a few very simple custom Python extensions, and then go develop a complete custom application in TG. But now you want to share some aspects between the two systems, for example you'd like to have authentication done in only one place, or you'd like to apply common headers and footers to both applications, again in just one place. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
