IntroductionIntroduction
    <Access Control>Access Control<Access Control>Access Control
    <Version control>Version control<Version control>Version control
    <Templates>Templates<Templates>Templates
    <RXML>RXML<RXML>RXML
    <Editors>Editors<Editors>Editors
  Content EditorContent Editor
  Editing filesEditing files
  Version ControlVersion Control
  Work areasWork areas
  LogViewLogView
  IntraSeekIntraSeek
 
Templates

One of the features of SiteBuilder is the use of templates to ensure a consistent layout and graphic profile and to assist in having a good navigation system throughout the site. Also, the templates lets the content editor focus on the content he is writing, instead of worrying about HTML and layout.

A template is a file that contains directions for how the page is to be built. It specifies how the headlines on the page will look, where on the page the ordinary text will be placed, whether there should be a navigation system on the page and, if so, how it will look and where it will be placed. In a way, a template may be seen as a mold into which the text is poured: If you select a simple template, the resulting page will be rather simple, while an ornate, complicated template may transform the same text into a page with graphical headlines, menus, a search engine and options to edit the text.

Frameworks and new tags
This is done in two ways. Firstly, the way to make a consistent layout is to have much of the HTML being similar from page to page. If we need a blue bar with a company logo on the top and bottom of every page, then we need to make sure that the code for producing that blue bar is at the beginning and end of every document. The easiest way to do this is to write a framework page, a page which consists of all the necessary elements to make up the layout, and then designate a spot in the framework where the variable content of the page should go.

The other way is to define new tags. Since the Roxen Challenger server allows for using RXML tags, and even defining new tags, we can make the tags do what we want them to do. If we would like an ordinary header, such as <h1>, to be rendered as a graphic element using the RXML tag <gtext>, then we simply redefine <h1> to be a new RXML tag that translates into a command for rendering graphical text. If we want to make sure that no flashing elements appear on the pages, we may redefine the <blink> tag into an RXML tag that does absolutely nothing.

Templates in use
Usually all pages of the same kind, such as product presentation pages or intranet document pages, should use the same template. This means that the pages get a consistent layout and feel, of course, but it also means that it will be easy to make site-wide changes to that layout. Adding an extra link to the Christmas Special Offer to every page on the site is as easy as putting it into the framework of the products template, instead of having to edit the page for every product the company offers.

Additionally, the template may supply the content writers with extra tags. An intranet template may supply its writers with tags for adding the company logo to the text or tags to mark a word for inclusion in a site wide index page.

Schematic example
The template system works together with the other systems of SiteBuilder. This schematic picture may illustrate the way from content file to the page presented to the user.


  1. A content file, consisting of some text and a picture.

  2. The content file together with a template. The template added some color and a headline.

  3. The next step is to add a navigation menu.

  4. Finally, the access control system is invoked, and a few of the menu choices are removed since the requesting user does not have permission to access them.
This is all done internally in SiteBuilder. Now, after all the systems of SiteBuilder has been working on the page, it is ready to be sent to the requesting user.