Note: instead of the user.* templates you can also use the new ar\events functionality. This will eventually replace the approach below.

Ariadne uses templates for everything it outputs. You can define any number of templates and use any kind of output format, not just html or xhtml, it can just as easily be PDF, XML or anything else.

This section describes the default templates in Ariadne, these are used to do common tasks, display Ariadne's user interface, etc. A number of these influence how Ariadne works or how your site works. These special templates are:

config.ini This template allows you to load template libraries, configure library settings or add your own site wide settings.
editor.ini This template defines the behaviour of the WYSIWYG editor as well as a number of related modules, like the html cleaner, html tidy, etc.
typetree.ini Th. is template defines which types of object are listed when creating a new object. It also defines their names and icons.
user.notfound.html This template is called by Ariadne whenever the requested page cannot be found. Ariadne will search for the nearest fitting object, which still matches the requested URL and call this template. You can redefine this template to make your own custom 404 error pages.
user.languageselect.html This template is called whenever a page is requested in a language which is not available. The default action is to show a list of language which are available, but you can redefine this to do something different.
user.workflow.*These templates are called whenever objects are saved or deleted.
view.html This is the default template, you can compare it to index.html in a traditional website. If no template is specified, Ariadne will assume this is the template you want to use.