Package com.epicentric.template

Provides classes and interfaces that encapsulate look-and-feel aspects of the end-user site to simplify customization and subsequent upgrades of the site.

See:
Package Summary

Interface Summary

Branding

Provides look-and-feel information for the current request.

Class Summary

BrandingSessionIdentifier	The serializable Object to be saved in the session to identify a Branding Object for a user.
BrandingUtils
Style	A Style is a specific instance in a Template category.
StyleUtils	Some convenience methods for dealing with Styles.
Template	Templates are categories of Styles, where each Template object corresponds to a single template.
Template.StyleSearchFilter
TemplateManager	The TemplateManager class is a single-instance class which is used to create, retrieve and store Template objects.
TemplateManager.TemplateSearchFilter
TemplateUtils	Some convenience methods for dealing with Templates and Styles.
ThemeManager.ThemeSearchFilter
ThemeProperty	Abstract class defining the properties of a theme.
ThemePropertyManager
ThemePropertyUtils	Convenience methods for dealing with ThemeProperty objects

Exception Summary

InvalidFileTypeException
TemplateStoreException

Package com.epicentric.template Description

Provides classes and interfaces that encapsulate look-and-feel aspects of the end-user site to simplify customization and subsequent upgrades of the site. The end-user pages of a site contain a number of presentation elements called templates. Most templates represent a region of a page--for example:

• Header defines the area at the top of the page, where a branding image is often displayed. A link to the administrative site might also appear in this region.
• Horizontal Navigation defines a horizontal layout for the menu items that link to the pages that make up the site; Vertical Navigation defines a vertical layout for these menu items.
• Chrome defines the elements that wrap around the content of each portlet. Depending upon its style, chrome can include the portlet's title and any buttons enabling end users to interact with it (such as edit and delete buttons).
• Footer defines the area at the bottom of the page and may consist of branding, company contact information, additional links, etc.

Each template can have any number of styles associated with it. Whereas a template is an abstract entity, a style is a particular implementation of that entity that displays in a particular way. For example, each template might have Modern, Retro, Classic, and Holiday styles. Site administrators can dynamically modify the look and feel of a site by simply selecting different styles for the various templates.

Both templates and styles have permissions associated with them. Within the Vignette Portal administration GUI, templates are referred to as style types.

Whereas templates and styles define the appearance of specific regions of a page, the location of each region is defined by a style known as a grid. Grids can include any combination of templates. For example, one grid might specify the location of a header, a footer, and horizontal navigation, whereas another grid might include both horizontal and vertical navigation. Vignette Portal ships with a number of grids.

For details about templates, styles, and other customizable components of a site, see Vignette Portal Developer's Guide available from Vignette Global Marketplace at http://global.vignette.com.

See:
Discussion

See Also:

com.epicentric.portalbeans