Content/layout templates are the templates that form the upper layers of a page’s template hierarchy. These templates typically do not include navigational interfaces but instead provide a definition for how the pages’ real content looks. Content templates can be very rigidly or loosely defined, thus enabling very tight control over what the end user can and cannot edit.
CommonSpot provides a number of ready-made templates that can incorporate the “look and feel” of the Web site and offer typical formatting and layout options. These basic forms can be filled directly with content and published as Web pages, or they can be modified to make customized pages. The same template can even serve very different purposes from one department to another.
With the pages’ basic framework in place, authors simply click where directed, and pop-up wizards in the blank regions guide them through the submission of content. The content is immediately integrated into the predefined structure of the template.
Any user who has template-creation rights (which are granted by the site administrator) can easily modify templates to satisfy precise needs. The result is a corporate-wide development process in which the people who best understand the content develop the templates.
Two varying content templates are pictured below. The first shows one of the standard predefined layout templates that comes out of the box with CommonSpot, the second is a specific Simple WYSIWIG template. Both templates define the elements and layout of the white space, and derive from the navigational template, which provides the common toolbars. However, the announcement template defines a specific header using Metadata fields in Rich Text Editor field (see the Enhancing Templates with Metadata section of this document for more information) and the Textblock element, which the content contributor must use to enter content. In the announcement template, the page header and layout control will be ‘locked down’ (see the Locking Down Templates section in this document for more) so that the content contributor who uses this template to create pages is restricted to only adding content to the Textblock element.