Zope, Plone, and Volto

by Kevin — published Oct 31, 2026

While I only decided to jump back into Zope and Plone very recently, I've been reading a lot about both of them. I will be discussing some of the key developmental differences for each of them here.

Zope Products

You could probably call this low-level web framework development, if you decide to write a Zope Product.  Plone itself is technically as Zope Product, a fully featured content management system, a CMS if you will.  If you are building a more specialized Python web application, and don't really need the content management of Plone, then you can just develop a pure Zope Product.

Native Zope Product

I am using the term here native, as it is a Zope Product that is otherwise meant to run on pure or vanilla Zope without any Plone site.  This can also be a secondary virtual hosted Zope site on a Plone instance, but doesn't use or share any Plone assets.  For example, when you typically deploy a Plone site out, you use the Plone site wizard on the start page to configure a new Plone site, this is usually called Plone by default, and sits at /Plone.  It is also possible in this portion of the website to access the Zope Management Interface.  In the ZMI, you can then create another folder at the root, and then point another virtual host to point there, such as a sub-domain, and rather than this sub-domain running a Plone site, it is instead running a standard Zope site.  One problem I've had with this specific configuration, is that a proper acl_users is not created, so you will either need to create a special page script to create the standard User Folder object, log in from a user in the main acl_users, or copy and paste an existing acl_users folder into this one.  The reason this sounds so confusing is because of Zope's new CSRF support, and a bug for when it comes to creating new User Folder containers, Zope cannot create it.  When you choose the option from the add list, it will perform a GET request to the constructor directly, with a majority of addable Products, they have a form you need to fill out before the object is created, usually at least the Id.  Then the user presses the submit button which will send the data over as a POST request.  Zope's new CSRF support forbids any GET request from modifying any data on the server, only POST requests can modify any server data.  So, this CSRF support is actually blocking the creation of Products which do not have a constructor form to fill out by the end-user.  So be very aware of this.

Plone friendly Zope Products

These are Zope Products which use Plone's main_template Page Template and it's macros to keep their Zope Product with a consistent theme within a standard Plone website.  I doubt many current Zope Products would be in this category, which does limit their overall reach and potential.  These Plone friendly Zope Products also don't need to use any Plone features or it's API, it can otherwise just be a regular Zope Product that just so happens to allow it's Page Template to work with the Plone website's template.  There's not much else to say about this.  Except that I am currently trying to figure out if I can easily make a Zope Product work with the Plone website theme, but also work perfectly find outside of Plone.  I think looking more into how these Page Templates are working should help me find a way to allow for this.

Zope Products with Plone Integration

This has not been tested, although I don't see why a Zope Product couldn't use any Plone's APIs.  I'll see about making a proof-of-concept, and depending on how it goes, I'll make a new follow-up blog post to discuss it.

How Zope Products work?

A Zope Product is usually contained in a single Python class, and sub-classes several other classes to give it it's general capabilities.  Each function of this class that has a docstring can the be access from the Internet, and is considered published.  There is a special class which needs to be used to add additional security, namely permissions to product functions which should only be accessed with the correct permissions.  Modern Zope also supports the typical Python function decorators for this as well, similar to how View functions in Django can be decorated to add permissions.

By far the easiest way to develop a new Product class for Zope is to use the PropertyManager Mixin if you can.  This can allow the Zope Management Interface to automatically generate a form for editing all the properties you tell it to manage.  Similar to how the Django Admin worked, but I think this is a lot easier actually.  These properties can then be effortlessly access or changed via one of the functions on the View class when called.

As mentioned, it's possible to call View functions over the Internet if it has a docstring, but this is very limited, and not really how they are meant to be used.  Instead, you need to create a Page Template to be used as your new Product's external view outside the ZMI.  This does make it possible for even a standard SimpleItem in Zope to have multiple views.  The view which will be the default will be the index_html function, which can either be a PageTemplateFile, which is what you should do, or a Python function on the class.  Inside the Page Template, it will be-able to reference any of the functions or properties of the Product class through context/calcMortgage for example.  The Page Template will insert the result of calling that function in this example.

Other than the constructor parts, that is how a typical Zope Product works, and it's not really all that confusing or having an apparent steep learning curve.  Once I understood the basic concepts and developed a very basic template class to use for any new Product, it's really easy to work with and use.  I am planning on making a proper video to show how a Zope Product in made in the near future, which is why I didn't bloat this post with a ton of examples.  This post is more theory than trying to be a full tutorial.

Plone Add-ons

I am still a bit new to Plone Add-ons, but will try to explain it from my current knowledge.  Both this section and the Volto section here will be rather barebones unfortunately.

With Plone, there is less centralization of the code, which can actually make it a bit difficult to learn and understand at first.  I found that the learning curve for Plone might actually be higher than that for Zope.  To create and manage Plone add-ons, I am using a command-line tool called plonecli, which is able to generate a full project directory, along with many basic defaults already configured.  This same plonecli command can then also add specific Plone components to this new Add-on project.  I haven't tried them all out yet, as I haven't found a real purpose to use some of them yet, but will probably go through each one.  Here are the add-on types you can create, and a bit of what I know about them.

behavior

This one I haven't really used much for anything yet, but have read the documentation, and here is what I can say about it.  This acts like a reusable component, in a way similar to concept as a visible component in an Integrated Development Environment, where you'd drop a set of components on.  It's also a bit different, in that yes, you can create several content types that share a single behavior to give them all that similar functionality.  One example in Plone is the Basic information behavior, which just adds in very common fields like Title, Description, Tags, and other stuff you might always want.  Then, this same behavior can then control how these new components work, how to parse the input, or render some output into them.

content_type

This is used to create what is called a Content Type.  In traditional programming, this would essentially be what is called the Data Model.  Here is where you can describe all the field/properties that this new Content Type will have.  Logic can also be associated to the Content Type, in the form of functions on the content class.  This is most similar to how in a Zope Product, the Product class had public functions which could be called from the Page Template.  This is essentially that, minus the ability to specify any Page Template to use, this is purely for the logic of how this  Content Type will function.

controlpanel

I haven't created one of these types yet, but I'm assuming it's related to creating custom Plone control panels, as it's name fully implies.

form

Another one I've only been reading the documentation for, but haven't yet created one in practice.  From what I understand, this is meant as a form to be displayed usually for managers so that can submit some sort of information.  It can also work with Content Types I believe, so it can have all it's properties and functions available in it's context.

indexer

Yet another one I haven't used in practice, assume it's used with the Plone Catalog.

portlet

Portlets are these small pieces of information along the side columns of a page, and a strip along the bottom.  An example Portlet used on this website is with the News frame you see on most pages to display the most recent website News.  I haven't designed one of these yet either, but probably will soon.

restapi_service

This one is for working with the REST API in some capacity, probably creating a custom endpoint of sorts.  I haven't used this one yet either.

site_initialization

Not sure what this would be, but I have a few thoughts.  One is that it's code that runs as soon as the Plone site starts each time to do some special configurations of sorts.  My other thought is that it's meant to add a new site profile wizard to the main page, allowing a fully working site through one of these templates.  Haven't used this one either.

subscriber

This one is meant for object or content type subscriptions, such as being notified when an object has changed.  I haven't used this one yet.

upgrade_step

This one is to add an upgrade step, so when you update your add-on, certain steps are taken to ensure the objects update correctly.

view

This is used for the creation of a new view, which can then be called from say a Content Type to display custom properties correctly.  The view also has an associated View Class, which can have various functions which the Page Template can call to perform specific calculations.

viewlet

I haven't used this one yet, but from what I've read, it's like a widget of sorts, that can be used in various places on the website.  I'll need to look into this one more.

Volto Add-ons

I haven't created a Volto specific add-on yet, but from my understanding they are created through the same Add-on as the Plone one mentioned above, but then have some additional types which I didn't mention above.  As mentioned, I still haven't worked with Volto yet, and so this section won't contain much more.  From what I've read is that a Volto Add-on is a mix of backend Python code, along with some front-end React code.