This presents a convention that allows models to be displayed in certain ways:

For instance, for a list of blog entries: diario/entry_archive_day.html … {% represent entry as “summary.html” %}

diario/entry_archive.html … {% represent entry as "summary.html" %} diario/entry_detail.html … {% represent entry as "detail.html" %}

Each template is placed in representations/diario.entry/

The power of this convention is revealed when you do something like a search engine that may be a list of different content types:

{% for object in search_result_list %}
    {% represent object as "search_result.html" %}
{% endfor %}

Project Home – http://code.google.com/p/django-representations/
Grab the Repository – svn checkout http://django-representations.googlecode.com/svn/trunk/