Skip to end of metadata
Go to start of metadata

Basic Themes

All basic rebranding of the IMS interface is performed using the Theme Editor (located in the Configuration > Manage Themes menu when logged in as an administrator). This Theme Editor allows you to create specific look and feel packages which can then be assigned either to the site as a whole or to individual users and events. You can have any number of themes and do not need any technical knowledge for most changes.

The theme editor is intended to allow you to change key palette colours and the logo graphic used by the standard theme provided with IMS.

For more information on Themes, see Themes and Languages

Advanced Templates

IMS is equipped with an advanced template engine, using the open-source standard templating language, Smarty. Each page of IMS is templated and can be edited from Configuration > Manage Themes page.

In each template, the HTML framework for the corresponding page or email in the main IMS product is provided for open-ended customisation. Variables, explained in the comments at the top of each file, are offered so that these can be included.

Although the template system is designed for experts, in some cases a change may be a simple text adjustment. In this case, please use the IMS Languages feature instead of templates.

Please be aware that when a .tpl file is changed, it is no longer automatically updated to track updates made by Third Light from time to time. Although this will not break your site, it may mean that eventually the theme will need to be manually re-synchronised with Third Light’s to use newer features.

A Smarty Crash Course may be found at http://www.smarty.net/crashcourse.php

Stylesheets

Stylesheets are edited through the same template system. The file template_css.tpl (version 5), or the files css.type.tpl (version 6) contain stylesheet elements used by the default XHTML. These files may be edited, or you can upload a .css file and refer to this in your templates if you prefer to leave them untouched (this is generally to be preferred).

For more information on adding stylesheets, see Generic content

  • No labels