devel:blueprints:django_template
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
devel:blueprints:django_template [2010/01/13 12:07] eide context processors as a table |
devel:blueprints:django_template [2010/01/13 12:16] (current) eide a little 'bout the base template |
||
|---|---|---|---|
| Line 5: | Line 5: | ||
| ===== Django systems ===== | ===== Django systems ===== | ||
| - | Something smart here | + | In the lib-python directory there's a base template, simply called base.html. Subsystems should extend this one (probably with their own base.html) and the base_content block in it. |
| + | |||
| + | base.html provides the header and footer for pages, so subsystems need only contribute the content. | ||
| ==== Context processors ==== | ==== Context processors ==== | ||
| Line 58: | Line 60: | ||
| 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. | 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. | ||
| + | |||
| + | MainTemplate will automatically populate the needed instance variables for the Cheetah compability class. | ||
| ==== Additional <head> content ==== | ==== Additional <head> content ==== | ||
devel/blueprints/django_template.1263384460.txt.gz · Last modified: 2010/01/13 12:07 by eide
Page Tools
