Personal tools

Contact Us 24/7 > 1 866.SIX FEET

Skip to content. | Skip to navigation

Home > Blog > Improving the Plone Setup Process

EVERYONE.NET SCHEDULED MAINTENANCE will be performing maintenance on their databases Friday October 28th, 2016 between 9:00PM PT to 3:00AM PT / 12:00AM ET to 06:00AM ET. During this time, all services including web mail, POP, IMAP, and SMTP relay may experience degraded performance and inbound mail delivery delays. We apologize for any inconvenience.


Improving the Plone Setup Process

written by Chrissy Wainwright on Thursday June 5, 2014
Comments | Filed under: ,

For starting a new Plone site from scratch, most in the Plone community are familiar with using Templer/ZopeSkel. Here at Six Feet Up, we have our own customized version called SixieSkel. SixieSkel makes it easy to get started on new projects, because the customized templates are set up to already use our processes.

Many projects we build tend to have three custom packages: project.policy, project.content (using ZopeSkel's archetype), and project.theme (zopeskel.diazotheme). Until recently, we would set up each one in its own repository, and add them to the buildout with mr.developer.

We have implemented some changes to our setup that will make these packages part of the buildout, all in the same repo, called a unified buildout. A major advantage for this is the ability to create atomic commits. It also makes our release process easier and faster since only the buildout needs to be tagged.

This change to a unified buildout made the initial project creation a bit difficult, as the packages still needed to be created separately, then modified to work with the buildout. This is what led me to update SixieSkel to automatically create a unified buildout for us.

When creating a buildout, SixieSkel will now ask four new questions:

  • Is this a unified buildout?
  • Add a content package?
  • Add a policy package?
  • Add a theme package?

So if you answer yes to all these questions, a is added at the root of the buildout, and each package is added into a folder named for the project (one of the first SixieSkel questions). Config files are also set up to expect the added packages so that once you run buildout, you can start up the site and have everything installed and ready to go, without touching any of the files yourself.

You can view the source code on Github, or setup and use SixieSkel locally, it is available at

$ easy_install -f -U sixieskel
$ templer sfu_buildout [project_name]
Posted by David Glick on Jun 06, 2014 03:54 AM
Thanks for sharing! I've also found it a good practice to put all client-specific code for a site in a single repository.
Posted by Marcin Staniszczak on Jul 25, 2014 06:11 AM
Nice:) But in example, better if it was: $ easy_install -i -U sixieskel instead of: $ easy_install -U sixieskel
Posted by chrissy on Jul 30, 2014 10:32 AM
Thanks, Marcin! I have updated that in the post.
Add comment

You can add a comment by filling out the form below. Plain text formatting.


Next Steps

Select a type of support:

Contact our sales team

First name:
Last name:
Phone Number:
Fight spam:
What is + ?
Call Us 1 866.SIX FEET