I work with (and on) a web application server, Zope, and use a content management platform built on top if Zope, named Plone. I sometimes am involved in fostering the emerging features that i need.

Plone With WSGI (started March, 2010)

Wanting access from Plone to web service facilities (in particular, Google App Engine) that exist outside of the Zope/Plone ghetto is seeming to mean running Plone hooked up with WSGI_, the python Web Server Gateway Interface [WSGI]_. There are existing recipes for this hookup, but the dust is far from settled, and unravelling what to use and how to use it involves ungainly much implicit knowledge. I try to shed some light on the territory i've discovered in the course of my progress finding a decent path to Plone under WSGI.

Plone Knit Points

Zope and Plone are infinitely extensible, and many extension measures involve plug-in points on many layers. I started to track many of the spots where things are tied together - knitted - in this compendium.

Plone Blobs

Large binary files (blobs) are increasingly essential ingredients of many websites, but Zope and Plone are only coming to have mainstream provisions for them. Needing such provisions for customer and personal projects, i've been eagerly using, and sometimes crafting, blob integration as preliminary measures are available.