Plone CMS: Open Source Content Management

DIY Plone Style

David Convent — 2011-02-16T02:13:02Z

This product is meant to be used as a base to develop a new theme (style) or skin (in the graphical meaning) for Plone, making use of the CSS and javascript Registries that now ship with the Plone package. Since version 2.5, DIYPloneStyle installs itself by making use of a GenericSetup profile (which ships with Plone from version 2.5 on as a replacement for the Quick Installer and the Customization Policies).

Starting a new skin project is made easy by the use of a generator script that creates a skeleton theme product (Python product on the file system) ready to hold your style elements (stylesheets, images, templates).

The provided example theme can be installed as a standalone product, it is what you get after walking all the way through Alexander Limi's step by step tutorial called Putting a new look on Plone: a real-world example. It is an early version of the skin that is deployed on the plone.net web site.

Full documentation on how to make use of this product, with many pointers to other resources on how the "Skins Tool" and the "Resource Registries" work, can be found in the tutorial about Creating a Custom Style for Plone.

Collective

Jon Stahl — 2006-04-23T22:25:00Z

The Collective is a community code repository for Plone Products and other add-ons, and is a useful place to find the very latest code for hundreds of add-ons to Plone. Developers of new Plone Products are encouraged to share their code via the Collective so that others can easily find it, use it, and contribute fixes and improvements.

Software home

John Samuel Anderson — 2009-01-09T20:20:00Z

The directory inside the Zope installation (on the filesystem) that contains all the Python code that makes up the core of the Zope application server. The various Zope packages are distributed here. Also referred to as the $SOFTWARE_HOME environment variable. It varies from one system to the next, depending where you or your packaging system installed Zope. You can find the value of this in the ZMI > Control Panel.

Zope instance

John Samuel Anderson — 2009-01-09T20:20:00Z

An operating system process that handles HTTP interaction with a Zope database (ZODB). In other words, the Zope web server process. Alternatively, the Python code and other configuration files necessary for running this process.
One Zope installation can support multiple instances. Use the buildout recipe plone.recipe.zope2instance to create new Zope instances in a buildout environment.
Several Zope instances may serve data from a single Data.fs using a ZEO server on the back-end.

Python path

John Samuel Anderson — 2009-01-09T20:25:00Z

The order and location of folders in which the Python interpreter will look for modules. It's available in python via sys.path. When Zope is running, this typically includes the global Python modules making up the standard library, the interpreter's site-packages directory, where third party "global" modules and eggs are installed, the Zope software home, and the lib/python directory inside the instance home. It is possible for python scripts to include additional paths in the Python path during runtime. This ability is used by zc.buildout.