This is a pre-production deployment of Warehouse, however changes made here WILL affect the production instance of PyPI.
Latest Version Dependencies status unknown Test status unknown Test coverage unknown
Project Description

This is a ZopeSkel template package for creating a skeleton Plone add-on
package. The skeleton package creates a Bootstrap Diazo (diaxotheme.framworks) childtheme package
and associated css and js resources for use with in
Plone 4.2+.

Use this package when you want to package a Diazo childtheme as a Plone add on,
particularly if you need to override viewlet or skin templates in the process.

This is a development tool. You should be familiar with Plone and buildout to
use it.

This package is compatible with ZopeSkel<3.0 only.


Add these lines into buildout::

parts =

recipe = zc.recipe.egg
eggs =

And run the buildout


Add ons under development are typically created in your buildout's src
directory. Command line for creating a package named diazochildtheme.mychildtheme would be::

../bin/zopeskel diazochildtheme diazochildtheme.mychildtheme

This will create a Python package with a directory structure like this::

|-- diazochildtheme
| +-- mychildtheme
| |-- diazo_resources
| | +-- static
| |-- locales
| |-- profiles
| | +-- default
| +-- template_overrides
|-- diazochildtheme.mychildtheme.egg-info
+-- docs

The typically customized parts are in the diazochildtheme.mychildtheme/diazochildtheme/mychildtheme subdirectory.


This is where you'll put your Diazo resources including a rules XML file and
one or more template HTML files. You may wish to interactively develop these
childtheme elements in the theming editor (for Plone 4.3+), then export the
resources and add them here.

A sample childtheme is included to use as a starting point. Just replace it if you
don't need it. The sample childtheme's key feature is that it makes use of all of
Plone's CSS and JavaScript as a starting point.

Everything you put in this directory and its subdirectories is publicly
available at ++childtheme++namespace.package/resourcename.ext.

NOTE: The Diazo childtheme will be available in Plone even if you have not
installed the package. It will not be applied, though, until enabled in the
ChildTheme configlet of site setup.


This is the conventional place to put static resources like CSS, JS and image files.
There's nothing magic about "static". Remove or replace it if it fits your needs.

Everything you put in this directory and its subdirectories is publicly
available at ++childtheme++namespace.package/static/resourcename.ext.


If your templates include translatable messages, you may provide translation
files in this directory. Ignore it if you don't need translations.

profiles, profiles/default

This is the Generic Setup profile for the add on. The is applied when you use
the "add ons" configlet in site setup to install the package.

This profile has a couple of important features:

* It sets up a BrowserLayer, which insures tha template overrides and registry
settings do not affect other Plone installations unless this childtheme is

* It has sample resource registrations for CSS and JavaScript resource
registries. These allow you to incorporate static resources which are part
of the childtheme into the Plone resource registries for efficient merging with
other CSS and JS resources. The samples are commented out. If you remove the
comment markers and install/reinstall the childtheme, the main.css and main.js
files from your diazo_resources/static directory will be incorporated into the
CSS and JS delivered by Plone -- even if the Diazo childtheme is not active.

The alternative to adding your resources to the registries is to load them
directly in your childtheme's index.html. This is a better approach if you don't
intend to use Plone's own CSS and JS resources. If you do, registering your
own resources will allow them to be merged for more efficient delivery.


You may use this directory to override any Plone viewlet, portlet or skin template.

To override a template, copy or create a template in this directory using the
full dotted name of the template you wish to override.

For example, if you wish to override the standard Plone footer, you would find the original at::

The full, dotted name for this resource is::

Template overrides are only applied when the BrowserLayer is installed by
installing your package. So, they won't affect Plone installations where this
package is not installed.

For details on template overrides, see the documentation for `z3c.jbot
<https:"" pypi="" z3c.jbot="">`_.


1.0 (2015-03-25)

* Initial release.
Release History

Release History


This version

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

Download Files

Download Files

TODO: Brief introduction on what you do with files - including link to relevant help section.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date (60.9 kB) Copy SHA256 Checksum SHA256 Source May 5, 2015

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS HPE HPE Development Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting