The Skin Demo
Master pages (sometimes called "master templates") can define a
look that several pages share. They wrap themselves around the
main or "slave" page, like a skin. If the master page isn't
specified, the default master of the closest ancestor of type
acs-subsite in the site map applies. This allows different
per-subsite skins around common pages. That's also called
"cobranding". The purpose of the "skin" package is to
demonstrate with a primitive example how
acs-templating supports this.
To get the subsite demo on your server, you need to perform the
following steps manually.
skin package. (At that point you can
read this documentation as
/doc/skin on your
Mount it on /skin.
Go to /admin/site-map on
- In the first row, "Main Site", follow "new sub
- Type "skin" in the box.
- Click "New".
- In the new row, "skin", follow "mount"
You'll find "Skin" at the bottom, under the centraized
services, which are usually not meant to be mounted.
Mount it (follow the link) anyway.
Create subsite "Curly" with another "api-doc"
You should still be at /admin/site-map.
Add another "new sub folder" to the "Main Site" as
"curly". Make it a "new application" called "Curly";
leave the application "ACS Subsite"
Add a "new sub folder" to "Curly" as "api-doc". Follow
"mount", then from the middle block (instances already
mounted elsewhere) follow "ACS API Browser" to create
Set different skins for subsites "/" and "/curly"
In the top row "Main Site", follow "set parameters"
Scroll to the bottom and change parameter "DefaultMaster"
to "/packages/skin/master/straight". (The "straight" skin
features a logo. It is hardcoded for simplicity, but
could be another parameter of subsite, or looked up in a
Click "Set Parameters" to submit your change.
Repeat the above steps for node "/curly", setting
"DefaultMaster" to "/packages/skin/master/curly"
Notice how these skins change the look of familiar pages:
Last modified: Fri Feb 23 15:22:12 EST 2001