This is an old revision of the document!
Table of Contents
Django templates in NAV
In the future NAV should mainly use Django templates, falling back to cheetah on old subsystems.
Backwards compability
MainTemplate.tmpl in webfront/templates is the main cheetah template. Most other cheetah templates includes this.
Compability with Django templates are done seamless. The MainTemplate includes nav.webfront.compability.Cheetah which provides two methods called footer and header. These two methods are simply printed, and thus the header and footer appears.
Additional <head> content
If a subsystem that uses Cheetah wants additional meta/CSS/JavaScript and/or other content that should go in the HTML head section to work it must appear in a subclass of one of the “additional” methods defined in the MainTemplate.
The methods are: additionalMeta, additionalCSS, additionalJavaScript, additionalHead.
Ie. if a subsystem wants to use foobar.css, it must appear in additionalCSS as such:
#def additionalCSS <link rel="stylesheet" type="text/css" href="foobar.css" /> #end def additionalCSS
