How it works?

by Volodymyr Rudnytskyy — last modified Dec 30, 2008 03:05 PM

Implementation description with an example

Solution is very simple. In a few words: all plone skin development are TTW. When skinning finished custom Plone skin product is generated by Plone Skin Dump with simple click. Resulting file-system product is based on custom skin layer selected by designer.
As illustration let's take a look at Alternative Plone Skins initiative before and after Plone Skin Dump is available.

Before. Alternative Plone Skins were distributed as .zexp of the custom skin layer lately. Users could manually install the skin following some simple steps.

After. At the moment all the skins are offered as file-system Plone skin products generated by qPoneSkinDump.

« Previous: What is qPloneSkinDump? Next: History »

Knowledge Base: The Knowledge Base is a place for free-form, community-mantained documentation. If you want to contribute, ask for collective access here.

About

You are reading:

from Creating Plone Skin Products with Plone Skin Dump.

This tutorial is helpful for Plone skins designers who have some experience with creating custom look and feel for Plone and want to release their work as file-system Plone Skin Product. Plone developers might find this product useful as well.

All content on a single page

Use with: Plone 2.5.x, Plone 2.1.x
Relevant for: Integrators, Customizers

This document was contributed by Volodymyr Rudnytskyy, and last modified 1137 days ago.

Visit our chat rooms or support forums if you have more specific questions.

You can also learn how to design, build, and deploy a website in Plone through one of the numerous Plone training sessions around the world.

Report errors, omissions, etc., to the documentation by emailing plone-docs@lists.sourceforge.net