Release 1.0 - ...

RenderTemplates provide the root SXML for rendering individual items in iXperion. They are mapped to channel-contenttype combinations. When the Publication Engine loads an item for rendering, the RenderTemplate data is looked up for the item's contenttype in the current channel, and the data in the body of the RenderTemplate will be fed to the SXML parser. Simple as that.

Mostly, especially when using ELBA, system translations and their optional RenderTemplate-local translations will be called from the RenderTemplate body:

Smartsite SXML CopyCode image Copy Code
<se:xhtmlpage xmlns:se="">
<html xmlns="">
 <body onload="onLoad();">
Since the RenderTemplate body SXML is the first data the SXML parser processes, the root-element must include a valid namespace declaration, and a single root-element. A few specialized macros exist for rendering specific web assets like HTML, XHTML:

  • HtmlPage
    Generic HTML template, providing DocType, Encoding
  • XHtmlPage
    Specialized XHTML Page template. Provides XML directive
  • AIM
    Specialized container for AIM scanning

In fact, the root element can be any SXML macro. For instance, binary data is served using a region macro, which contains a binary macro for the actual data sending.

Smartsite SXML CopyCode image Copy Code
<se:region xmlns:se="">
 <se:cachefile />
 <se:binary field="binarydata" />