Document Actions
Tips for creating your own Plone Themes
Some useful tips for making your site designs stand out and work well with future versions of Plone.
In this tutorial, Alexander Limi will show you how to take a default Plone site and put a totally different look on it. (Not updated for Plone 3.0)
Page
15
of
15.
Do's and don'ts for themes:
- Don't add behaviour
- You never know what kind of site you're going to live inside — keep Javascript and template changes (apart from changes to the purely structural templates like
main_templateorglobal_logo) outside the theme product. - Don't create external dependencies
- If you have a portlet that pulls data from an SQL database, that portlet should live in a separate product, not in the theme product
- Do reuse markup
- The headers in our example look very different from the original ones, but are still h1 tags.
- Do change the design slightly
- Don't be afraid to deviate a little bit from the designer's mock-up if it goes against good web usability rules — but be ready to defend it in front of the customer, and tell him why you did it differently.
by
Alexander Limi
—
last modified
May 17, 2006 - 21:51
Contributors:
David Convent, Reinout Van Rees
All content is copyright Plone Foundation and the individual contributors.
Thanks !
Many thanks to you Alexander, for this nice step-by-step introduction to the design of different-looking Plone sites. There have been a few hick-ups while I tried to follow you, but reference to the DIY tree was generally most helpful. Robert