Getting Started - The Manual Way
Preparing DIYPloneStyle for making it the skeleton of a new visual theme for Plone.
This file is where you will add your own CSS rules. 1 **Rename all the folders** which name starts with 'diystyle_base' in the 'skins/' directory to something that suits better your product name (2). 1 **In config.py,** change the name of your skin selection by modifying the 'name' value of the first entry in 'SKINSELECTIONS' (3). If your product won't provide more than one skin selection, you can remove the 'layers' key from that entry (make sure 'SKINSELECTIONS' match folder names in your skins directory).
Change 'DEFAULTSKIN' to make it use the name of your skin selection.
In the 'STYLESHEETS' declaration, replace 'diystylesheet.css' by the name you chose for that template, omitting the '.dtml' suffix. 1 **In Extensions/Install.py,** edit the relevant lines in the import declarations (see '# CHANGE' comments). 1 **In tests/testStyleInstallation.py,** replace all occurences of 'DIYPloneStyle' by the name of your product (see '# CHANGE' comment). 1 **Edit README.txt,** give it another description, remove the usage and credits paragraphs, and replace author names and email addresses.
If you plan to distribute your work, please leave a note stating that it is based on DIYPloneStyle. 1 **Clear HISTORY.txt** from its DIYPloneStyle related content. 1 **Remove the basic example** - **Remove all the files** which name starts with 'diystyle_example' in the 'skins/' directory. - **In config.py,** in the 'SKINSELECTIONS' declaration, remove the lines declaring the 'DIY Style Example' skin. 1 **Remove the bin/ folder** as the script it contains only works on a clean, left unmolested version of DIYPloneStyle. **That's it!**
Now you can test the initial state of your visual theme by restarting the Zope server and installing it from the *Site Setup > Add/Remove Products page* (as manager, in the Plone interface). Your Plone Site should now look like this:
**Now have fun with your new project!**
Troubleshooting --
This part of the tutorial is likely to be the one that will put you into
some trouble.See the "Troubleshooting":troubleshooting section of this tutorial if you feel that you are in a desperate situation.
(1) It is safer to work with a copy of the product so that it's easy to compare with the original version if you feel like in trouble. back
(2) Unless you configured it otherwise in the 'config.py' module, any folder located in the 'skins/' directory of your product will be registered as an *FSDirectoryView* with the portal skins tool. Because *FSDirectoryViews* must have a unique name/id in the skins tool, good practice is to include your product name into folder names to ensure these don't clash - particularly when using a name that might be commonly used. back
(3) In versions prior to 1.0.3, the name of the skin selection is setup using the 'SKINNAME' variable. back
Previous:
Installation and basic example
