%TOC% %STARTINCLUDE%
# TWiki Template System
_Definition of the templates used to render all HTML pages displayed in TWiki_
## Overview
The new modular template system is more flexible, efficient, and easily updated than the old set-up, where each template is a complete HTML file. The new master template approach places common templates parts, like headers and footers, in one shared file. This simplifies the conversion of templates into XHTML format, and provides a more versatile solution for templates and for [[TWikiSkins]].
## Major changes from the previous template system
The main difference is that templates are now defined using variables to include template parts. You change one stored instance of a common element to update all occurrences. The new system:
* separates a set of common template parts into a base template that is included by all of the related templates;
* defines common variables, like a standard separator (ex: "|"), in the base template;
* defines variable text in the individual templates and passes it back to the base template.
## Functional Specifications
* Special template directives (or preprocessor commands) are embedded in normal templates.
* Use of template directives is optional, templates work without them.
* All template preprocessing is done in `&TWiki::Store::readTemplate()` so that the caller simply gets an expanded template file (the same as before).
* Directives are of the form %TMPL:<key>%
and %TMPL:<key>\{"attr"\}%
.
* Directives:
* %TMPL:INCLUDE\{"file"\}%
: Includes a template file. The template directory of the current web is searched first, then the templates root (`twiki/templates`).
* %TMPL:DEF\{"var"\}%
: Define a variable. Text between this and the END directive is not returned, but put into a hash for later use.
* %TMPL:END%
: Ends variable definition.
* %TMPL:P\{"var"\}%
: Prints a previously defined variable.
* Variables are live in a global name space, there is no parameter passing.
* Two-pass processing, so that you can use a variable before declaring it or after.
* Templates and [[TWikiSkins]] work transparently and interchangeably. For example, you can create a skin that overloads just the `twiki.tmpl`, like `twiki.print.tmpl`, that redefines the header and footer.
* **_Note:_** The template directives work only for templates, they do not get processed in topic text.
## TWiki Master Template
All common parts are defined in a master template, **twiki.tmpl**
, that all other templates use.
>
>
> Template variable: |
> Defines: |
>
>
> %TMPL:DEF{"sep"}% |
> "|" separator |
>
>
> %TMPL:DEF{"htmldoctype"}% |
> Start of all HTML pages |
>
>
> %TMPL:DEF{"standardheader"}% |
> Standard header (ex: view, index, seach) |
>
>
> %TMPL:DEF{"simpleheader"}% |
> Simple header with reduced links (ex: edit, attach, oops) |
>
>
> %TMPL:DEF{"standardfooter"}% |
> Footer, excluding revision and copyright parts |
>
>
> %TMPL:DEF{"oops"}% |
> Skeleton of oops dialog |
>
>
## Types of Template
There are two types of templates:
* **HTML Page Templates**: Defines layout of %WIKITOOLNAME% pages
* **Template Topics**: Defines default text when you create a new topic
### HTML Page Templates
%WIKITOOLNAME% uses HTML template files for all actions like topic view, edit, preview and so on. This allows you to change the look and feel of all pages by editing just some template files.
The template files are in the **twiki/templates**
directory. As an example, **twiki/templates/view.tmpl**
is the template file for the **twiki/bin/view**
script. Templates can be overloaded per web. The following search order applies:
1. **twiki/templates/$webName/$scriptName.tmpl**
2. **twiki/templates/$scriptName.tmpl**
**_Note:_** `$webName` is the name of the web (ex: `Main`), and **$scriptName**
is the script (ex: `view`).
**_Note:_** [[TWikiSkins]] can be defined to overload the standard templates.
Special variables are used in templates, especially in `view`, to display [[TWikiMetaData]].
### Template Topics
Template topics define the default text for new topics. There are three types of template topics:
>
>
> Topic Name: |
> What it is: |
>
>
> Web Topic View Template? |
> Help text shown when you view a non existing topic. |
>
>
> Web Topic Non Wiki Template? |
> Help text shown when you view a non existing topic that has not a Wiki Name?. |
>
>
> Web Topic Edit Template? |
> Default text shown when you create a new topic. |
>
>
All template topics are located in the %TWIKIWEB% web. The [[WebTopicEditTemplate]] can be overloaded. The following search order applies when you create a new topic:
1. The topic name specified by the `templatetopic` CGI parameter.
2. WebTopicEditTemplate in the current web.
3. WebTopicEditTemplate in the %TWIKIWEB% web.
#### Template Topics in Action
Here is an example for creating new topics based on a specific template topic:
Above form asks for a topic name. A hidden input tag of name "templatetopic" specifies the [[ExampleTopicTemplate]] as the template topic. Here is the HTML source of the form:
<form name="new" action="%SCRIPTURLPATH%/edit%SCRIPTSUFFIX%/%WEB%/">
* New example topic:
<input type="text" name="topic" value="ExampleTopic%SERVERTIME{$yearx$mox$day}%" size="23" />
<input type="hidden" name="templatetopic" value="ExampleTopicTemplate" />
<input type="hidden" name="onlywikiname" value="on" />
<input type="submit" value="Create" />
(date format is <nop>YYYYxMMxDD)
</form>
The "onlywikiname" parameter enforces [[WikiWords]] for topic names.
**_Note:_** Use can use the %WIKIUSERNAME%
and %DATE%
variables in your topic templates as the signature; those variables are expanded when a new topic is created. The standard topic signature is:
-- %WIKIUSERNAME% - %DATE%
## Templates by Example
Attached is an example of an oops base template `oopsbase.tmpl` and a example oops dialog `oopstest.tmpl` which is based on the base template. **_NOTE:_** This isn't the release version, just a quick, simple demo.
### Base template oopsbase.tmpl
The first line declares the delimiter variable called "sep", used to separate multiple link items. The variable can be called anywhere by writing %TMPL:P\{"sep"\}%
>
>
>
> %TMPL:DEF{"sep"}% | %TMPL:END%
> <html>
> <head>
> <title> %WIKITOOLNAME% . %WEB% . %TOPIC% %.TMPL:P{"titleaction"}%</title>
> <base href="%SCRIPTURL%/view%SCRIPTSUFFIX%/%WEB%/%TOPIC%">
> <meta name="robots" content="noindex">
> </head>
> <body bgcolor="#FFFFFF">
> <table width="100%" border="0" cellpadding="3" cellspacing="0">
> <tr>
> <td bgcolor="%WEBBGCOLOR%" rowspan="2" valign="top" width="1%">
> <a href="%WIKIHOMEURL%">
> <img src="%PUBURLPATH%/wikiHome.gif" border="0"></a>
> </td>
> <td>
> <b>%WIKITOOLNAME% . %WEB% . </b><font size="+2">
> <B>%TOPIC%</b> %TMPL:P{"titleaction"}%</font>
> </td>
> </tr>
> <tr bgcolor="%WEBBGCOLOR%">
> <td colspan="2">
> %TMPL:P{"webaction"}%
> </td>
> </tr>
> </table>
> --- ++ %TMPL:P{"heading"}%
> %TMPL:P{"message"}%
> <table width="100%" border="0" cellpadding="3" cellspacing="0">
> <tr bgcolor="%WEBBGCOLOR%">
> <td valign="top">
> Topic <b>%TOPIC%</b> . {
> %TMPL:P{"topicaction"}%
> }
> </td>
> </tr>
> </table>
> </body>
> |
>
>
### Test template oopstest.tmpl
Each oops template basically just defines some variables and includes the base template that does the layout work.
>
>
>
> %TMPL:DEF{"titleaction"}% (test =titleaction=) %TMPL:END%
> %TMPL:DEF{"webaction"}% test =webaction= %TMPL:END%
> %TMPL:DEF{"heading"}%
> Test heading %TMPL:END%
> %TMPL:DEF{"message"}%
> Test =message=. Blah blah blah blah blah blah blah blah blah blah blah...
>
> * Some more blah blah blah blah blah blah blah blah blah blah...
> * Param1: %PARAM1%
> * Param2: %PARAM2%
> * Param3: %PARAM3%
> * Param4: %PARAM4%
> %TMPL:END%
> %TMPL:DEF{"topicaction"}%
> Test =topicaction=:
> [[%WEB%.%TOPIC%][OK]] %TMPL:P{"sep"}%
> [[%TWIKIWEB%.TWikiRegistration][Register]] %TMPL:END%
> %TMPL:INCLUDE{"oopsbase"}%
> |
>
>
### Sample screen shot of oopstest.tmpl
With URL: **.../bin/oops/Test/TestTopic2?template=oopstest¶m1=WebHome¶m2=WebNotify**
>
>
> |
>
>
## Known Issues
* A drawback of referring to a master template is that you can only test a template from within TWiki, where the include variables are resolved. In the previous system, each template is a structurally complete HTML document with a `.tmpl` filename extension - it contains unresolved `%VARIABLES%`, but can still be previewed directly in a browser.
-- [[PeterThoeny]] - 23 Jul 2001
-- [[MikeMannix]] - 14 Sep 2001