Red Innovation Skin
Visual theme for Plone 2.1
Version 0.5
Copyright
Copyright 2006 Red Innovation
This product includes code from DIYPloneSkin 1.0.4 product copyright David
Convent and Martin Aspeli.
Description
Look sexy. Look cool. Look better than others.
Features
-
Red color scheme
-
Wordpress stylish mainframe with a dominating top image
-
Portlets with smooth image frames
-
Drop shadows
-
Metallic button polish
-
Search portlet
-
Layout shrinks gracefully when narrowing the viewport
-
Graceful degeneration when images are disabled
The skin was built www.redinnovation.com
site in mind. For your own site, you need to do some advanced customization.
Due to drop shadow and other effects, changing the logo, color scheme, etc.
might not be so straightforward process. Paint Shop Pro template images for the
skin are included.
License
Requirements
-
Tested with Plone 2.1.2, othet versions might not work
Installation
-
Extract product to your Plone/Data/Products directory
-
Use Plone quick installer to install the product
Customizing
-
You need to change customize global_logo.pt and footer.pt files with your
own logo and copyright texts.
-
Go to Zope Management interface, choose Plone -> portal_skins
-
Choose Ruby Red
-
Click either footer, logo_animated or logo_text. The logo is divided to
two parts. You can disable the other part if you can have logo in one piece.
-
Click customize
-
Now you can edit your custom items in portal_skins/custom folder
-
All portlets must be changed to use portlet slot mechanism introduced in this
skin. This skin is shipped with modified
-
portlet_navigation
-
portlet_login
-
portlet_prefs (Preferences)
-
portlet_search
-
Add portlet_search to ZMI -> Plone instance -> Properties ->
left_slot, since there is no longer search filed in main_template
References
The skin is in live usage in www.redinnovation.com
Quality assurance
The skin is tested with:
-
Plone 2.1.2
-
Zope 2.8.5
-
Windows XP
-
IE 6.0
-
Opera 8.5
-
Firefox 1.5
Known problems
-
The skin is quite heavy and in its current form is not suitable for mobile /
text-only / accessibility demanding sites
-
Some of administrative interface buttons are not skinned propeply
Todo
-
Convert from <table> based layouts to nested divs. <table> should
not be used for layouting since it confuses screen reader software and hinders
accessibility. Even using <table> elements is a dirty and fast
solution, <table> elements seem to have better cross-browser
compatibility than nested divs, relative positioning, etc. advanced CSS stuff.
-
CSS optimizations - remove overlapping style definitions
-
Image optimizations
Contact
For support, contracting, etc.
mikko@redinnovation.com
www.redinnovation.com
Changelog
Version 0.5