This page describes the format of the skin template files (.tmpl) that are used to create PmWiki skins. As described in the skins page, a skin is a collection of files that specifies the layout for PmWiki pages. Each skin must include a template file that provides the skeleton for displaying a PmWiki page.
Template file format
A template file is basically an HTML file that also contains variable substitutions (indicated by ‘$’) and special directives embedded in HTML comments. Two special directives are required in the template file. The directive
There is also an optional
When PmWiki displays a page, it replaces the directives and variable substitutions with the values appropriate to the current page. For example, the
There is a long list of variables available for substitution in pages; some of the most useful include:
$PageUrl the url of the current page $ScriptUrl the base url to the pmwiki.php script $Title the page's title (e.g., "`SkinTemplates") $Titlespaced the page's title with spaces (e.g., "Skin Templates") $Group the name of the current group (e.g., "`PmWiki") $FullName the page's full name (e.g., "`PmWiki.SkinTemplates") $LastModified the page's last modification time $PageLogoUrl the url of a site logo $WikiTitle the site's title $SkinDirUrl the url of the skin's folder
This last variable,
The template is not limited to using the variables listed here; nearly any PHP global variable that begins with a capital letter can be used in a skin template. Page variables can also be used in templates.
Besides the required
If multiple pages are listed in the directive, then only the first available page is used. Thus
The markup directive processes any text that follows the colon as wiki markup and displays that in the output.
This directive calls a PHP function named “SomeFunction”, passing the current page’s name and the text following the function name as arguments. PHP functions called in this manner are typically defined in a local customization file. Args allows only one argument, which has to be splitted then.
A template file can designate “sections” that are included or excluded from the output based on page directives or other criteria. A section always begins with
<!--PageHeaderFmt--> (:noheader:) <!--PageFooterFmt--> (:nofooter:) <!--PageTitleFmt--> (:notitle:) <!--PageLeftFmt--> (:noleft:) <!--PageRightFmt--> (:noright:) <!--PageActionFmt--> (:noaction:)
Skin designers can define custom sections and markups, but currently all section names in the template must begin with “Page” and end with “Fmt”. As mentioned you also have to define the corresponding markup (for example in your config.php) like this:
Markup('noxyz', 'directives', '/\\(:noxyz:\\)/ei', "SetTmplDisplay('PageXYZFmt',0)");
Skins can also be internationalized by using
For example, the substitution
See Skins for how to change the default PmWiki skin. See also Cookbook:Skins, where you will find pre-made templates you can use to customize the appearance of your site. You can also create a file called local.css in the pub/css/ directory and add CSS selectors there (this file gets automatically loaded if it exists). Or, styles can be added directly into a local customization file by using something like:
Q Where can the mentioned “translation table” be found for adding translated phrases?