17. Write Your Own Python Add-On to Customize Plone#
In this part you will:
Create a custom Python package
Modify the buildout to install
plonecli, a Plone CLI for creating Plone packages
the structure of python packages
17.1. Creating the package#
You can skip this part since you already added
ploneconf.site as a source-checkout when running buildout.
And in Creating a Plone Site you installed that package when creating your site.
You can still follow this chapter to learn how to create your own packages.
Your own code has to be organized as a Python package. A python package is a directory that follows certain conventions to hold python modules.
We are going to use plonecli to create a skeleton package. You only need to fill in some blanks.
bobtemplates.plone that offers several Plone-specific templates for
mr.bob, a project template builder similar to
$ pip install plonecli $ pip install bobtemplates.plone==6.0b15
Then create the addon:
plonecli create addon sources/ploneconf.site
The new add-on will be created in the
You have to answer some questions about the add-on. Press Enter (i.e. choosing the default value) for most questions except where indicated (enter your GitHub username if you have one, do not initialize a GIT repository, Use Plone 5.2 and python 3.7):
--> Author's name [Philip Bauer]: --> Author's email [firstname.lastname@example.org]: --> Author's GitHub username: pbauer --> Package description [An add-on for Plone]: --> Do you want me to initialize a GIT repository in your new package? (y/n) [y]: n --> Plone version [5.2.4]: --> Python version for virtualenv [python3]: --> Do you want me to activate VS Code support? (y/n) [y]: n git init is disabled! Generated file structure at /Users/pbauer/workspace/training/buildout/src/ploneconf.site
If this is your first python package, this is a very special moment.
You generated a package with a lot files. It might look like too much boilerplate but all files in this package serve a clear purpose and it will take some time to learn about the meaning of each of them.
17.2. Volto Add-ons#
The package that will hold your own code for volto was already created when you installed the frontend with
frontend/ that you created in the chapter Installing the frontend not only holds the default volto frontend but also gives you the option to extend and customize the frontend.
When a python package is production-ready you can choose to distribute it as an egg over the python package index, pypi. This allows everyone to install and use your package without having to download the code from github. The over 250 python packages that are used by your current Plone instance are also distributed as eggs.
17.4. Inspecting the new package#
src there is now a new folder
ploneconf.site and in there is the new package. Let's have a look at some of the files:
You can ignore these files for now. They are here to create a buildout only for this package to make distributing and testing it easier.
The documentation of your package goes in here.
This file configures the package, its name, dependencies and some metadata like the author's name and email address. The dependencies listed here are automatically downloaded when running buildout.
The python code of your package itself lives inside a special folder structure. That seems confusing but is necessary for good testability. Our package contains a namespace package called ploneconf.site and because of this there is a folder
__init__.pyand in there another folder
siteand in there finally is our code. From the buildout's perspective your code is in
your buildout directory/src/ploneconf.site/src/ploneconf/site/real code
Unless discussing the buildout we will from now on silently omit these folders when describing files and assume that
your buildout directory/src/ploneconf.site/src/ploneconf/site/ is the root of our package!
The phone book of the distribution. By reading it you can find out which functionality is registered using the component architecture. There are more registrations in other zcml-files in this add-on (e.g.
permissions.zcml) that are included in your main
This holds code that is automatically run when installing and uninstalling our add-on.
Here a browserlayer is defined in a straightforward python class. We will need it later.
This holds the setup for running tests.
This holds the tests.
This directory is a python package (because it has a
__init__.py) and will by convention hold most things that are visible in the browser.
The phonebook of the browser package. Here views, resources and overrides are registered.
This folder is here to allow overriding existing default Plone templates.
A directory that holds static resources (images/css/js). The files in here will be accessible through URLs like
This directory can hold translations of text used in the package to allow for multiple languages of your user-interface.
This folder contains the GenericSetup profile. During the training we will put some XML files here that hold configuration for the site.
Version number and dependencies that are auto-installed when installing our add-on.
This seems like a lot of complicated boilerplate. In fact a Plone-package can be much smaller and simpler. See starzel/minimal for a minimal example. But as stated above the stucture of the package and every part of it serves a well-defined purpose.
When you are working on large projects you will appreciate the best-practices laid down in this package.
17.5. Including the package in Plone#
Before we can use our new package we have to tell Plone about it. Look at
buildout.cfg and see how
ploneconf.site is included in
auto-checkout += ploneconf.site # starzel.votable_behavior parts = checkversions instance mrbob packages robot test zopepy eggs = Plone Pillow # development tools plone.api plone.reload Products.PDBDebugMode plone.app.debugtoolbar Products.PrintingMailHost pdbpp # TTW Forms collective.easyform # The add-on we develop in the training ploneconf.site # Voting on content # starzel.votable_behavior zcml = test-eggs += ploneconf.site [test]
This tells Buildout to add the egg
ploneconf.site. The sources for this eggs are defined in the section
[sources] at the bottom of
[sources] ploneconf.site = git https://github.com/collective/ploneconf.site.git email@example.com:collective/ploneconf.site.git starzel.votable_behavior = git https://github.com/collective/starzel.votable_behavior.git pushurl=git://github.com/collective/starzel.votable_behavior.git
This tells buildout to not download it from pypi but to do a checkout from GitHub put the code in
ploneconf.site is now downloaded from GitHub and automatically in the branch master.
ploneconf.site can be called an egg even though it has not been released on pypi. Plone can use it like it uses an egg.
If you do not want to use the prepared package for ploneconf.site from GitHub but write it yourself (we suggest you try that) then add the following instead:
[sources] ploneconf.site = fs ploneconf.site path=src starzel.votable_behavior = git https://github.com/collective/starzel.votable_behavior.git pushurl=git://github.com/collective/starzel.votable_behavior.git
This tells buildout to expect
fs allows you to add eggs on the filesystem without a version control system.
Now run buildout to reconfigure Plone with the updated configuration:
After restarting Plone with ./bin/instance fg the new add-on
ploneconf.site is available for install.
We will not install it now since we did not add any of our own code or configuration yet. Let's do that next.
Create a new package called
collective.behavior.myfeature. Inspect the directory structure of this package. Delete it after you are done. Many packages that are part of Plone and some add-ons use a nested namespace such as
Open plone/bobtemplates.plone and read about the templates and subtemplates it provides.
You created the package
ploneconf.siteto hold your code.
You added the new package to buildout so that Plone can use it.
In one of the next chapter we will also create a add-on for Volto, the React frontend.