plone

Once upon a time customization of the Plone navigation portlet was easy. You just dropped a customized portlet_navigation.pt into a skins layer and presto.

In Plone3, customizing the navigation is still very easy. But it requires a bit more understanding of the component architecture.

Mailman is our mailing list software of choice. Even when using PloneGazette to format mailings, we prefer to use Mailman as the actual mail sender: it's faster, it has superior bounce handling, and it runs on our dedicated list server, outside our Plone environment.

Managing subscriptions for simple publication sites can be as easy as creating a MailManSubForm. However, if you have a full-fledged Member site you'll want to integrate mailing list subscription/unsubscription options as part of the member profile personalization experience in Plone.

We need to use the Plone Member database as master for the mailman database, in other words. This turns out to be quite easy.

Following Martin Aspeli's excellent buildout tutorial, in a clean chroot setup, has helped me rediscover the joys of programming. Because, let's face it: if Python is The Beauty, Zope2 surely is The Beast.

Zope3 is a much more gentile creature. It's availability within the bowels of modern Zope2 releases is a godsend, as any developer working with Plone3 will testify. Meanwhile, the Python community at large has rallied around the Python Package index and easy_install eggs as the primary channel for distributing code.

To leverage these new development practices, you need to be able to control your python environment. Read on to find out, why this is a problem, and what you can do about it.