Document Actions
Layer replacement in skin
For skin designers who use the same skin for many sites, except for a change of one layer that determines the look of the page (we will call this visual layer). This enables replacement of visual layer without replacing the skin.
Advantages:
- skin designer is more independent from a programmer.
- choose layer instead of skins: no need to have many unnecessary skins on site.
On the Plone Configuration menu, you can choose between different skins. With this approach however, we do not want to choose between different skins. We always want a certain skin to be selected, skin S, lets say. What we want instead is this: We want the list of layers that constitute skin S to change slightly - substitute visual layer A with visual layer B, for example - as described above.
This is done via the vsCore-configlet. The visual layer then sits on top of the vsCore layer, which in turn sits on top of the custom layer. To achieve the same result via the skin selection in Plone Configuration, one would have to install near-identical skins for each look.
This modification requires that the current skin is called 'vsSkin' and the 'visual layers' be installed inside a product called vsSkins; these titles can of course be easily changed inside the code.