This is a list of tasks to remind me what to do when porting a xdv theme to

Replace “my.theme” or “my/theme” with your theme namespace.

Use Plone 4.1

Migrate site to Plone 4.1 or add proper version dependencies to “extends” sections on buildout.

Add setuptools dependency on

Depend on on

 # -*- Extra requirements: -*-

Update GS Profile

If working on a egg, change the profile dependency from collective.xdv to On profiles/default/metadata.xml locate the following line:


And change it to:


Also create the file profiles/default/theme.xml with the following contents (This also enables the theme upon installation):


On the top level resource directory …

Change the rules.xml namespace. Open rules.xml (and other xml files) on you static directory. Change the xml namespace from:





Then, on my/theme/configure.zcml locate this line:

<include package="collective.xdv" />

And change it to:

<include package="" />

Move theme parameters to manifest.cfg

New features of include multiple themes and packaging themes in ZIP files.

Themes on ZIP files and themes developed on the file system can include a manifest.cfg file, with the classic INI file format, that includes the following:

title = My Theme
description = Description of your theme
rules = /++theme++my.theme/directory/rules.xml
prefix = /++theme++my.theme/directory

That file serves as a replacement for some settings that you’d normally insert into using registry.xml import step.