Zope Plone

I work with and have contributed to the development of a web application server, Zope, and a content management platform built on Zope named Plone.

    Contained Pages

    Plone6 Volto
    The new platform on which I've implemented my website, manually migrating from Plone 4 for the original version. I like the implementation of a block structured framework, based on React Semantic UI, by members of the Plone community has implemented.
    Plone4 WSGI
    The Web Services Gateway Interface is a specification for communications between and among web servers and web applications. It is officially stated in PEP 333 (a Python Enhancement Proposal), and it is a powerful basis for synthesizing web applications through the interconnection of components, over the web. It is complex, as are implementations of the specification in Plone. Around March, 2010 I attempted to get a handle on it and needed better guides than I found, so started to develop my own. I didn't go very far.
    Plone4 Blobs
    At several points from November, 2007 through March 2009 I worked with preliminary versions of Andi Ziedler's Plone/Zope integrations of binary large objects (blobs) in Plone 3, so my clients and I could include rich media - video, audio, formatted documents like pdf - on our sites without bloating ZODB file storage. In the process I got more familiar with zc.buildout , the Python automated build machinery used by Plone, in order to work out ZEO integration and other issues. This is an account that changed as the situation developed, and conveys many useful details involving building plone/zc.buildout, operation of blobs, and related things.