Skins are a way to provide branding and navigation for Self Service. The skin provides the entire HTML surrounding the current view.
Skins use a
SkinDefintion
item descriptor to provide the data for theindex.jsp
pageThe
index.jsp
page uses thestyle
attribute as the name of aSelfServiceSiteOption
that is included in the<head>
sectionThe
index.jsp
page uses thejavascript
attribute as the name of aSelfServiceSiteOption
that is included in the<head>
sectionThe
index.jsp
page uses thelayoutUrl
attribute to include the skin in the<body>
section. ThelayoutUrl
is included using a<dsp:include>
tagThe skin may define additional options using the
additionalOptions
attribute. The Skin Settings page in Service Administration uses thehint
attribute of theSelfServiceSiteOption
to determine which editor to place in the page. Valid values forhint
are:null
,int
,string
,longstring
, andBoolean
The skin JSP page should include the
view.jsp
page to render the actual viewThe skin needs to provide navigation for the application. The skin should have access to an object that lists all the currently available views
The skin author is responsible for providing the JSP page to be rendered, defining the SkinDefinition
instance in the repository, and setting up the SelfServiceSiteOptions
in the repository. The skin author must create at least a SelfServiceSiteOption
for style
and a SelfServiceSiteOption
for javascript
, even if the default value is empty. The skin author can define additional options that are used by the skin and these should be created in the repository.
Authoring a skin is a developer task. Configuring the SelfServiceSiteOptions
for a skin should be done in the Service Administration > Skin Settings page.