Hey man, your question is not entirely clear but:
If you dont want to repeat yourself, you typically would use extend
tags as everyone has said. These templates can be as deep as you want
it, (not sure about the performance impact) but you could have and i
have used this
Base Template
|-----Subtemplate
|---- Micro-template
Your URL calls the last template, which 'extends' the next level up,
which in turn extends the base.
The other option is, using a template tag i.e {% get_options %} and
automatically generating the HTML required (THis could be linked to a
queryset), the documentation on templatetags will help you there.
Regards,
Ismail
On Fri, Nov 13, 2009 at 6:36 AM, Andy Mckay <a...@clearwind.ca> wrote:
> On 09-11-12 10:35 AM, Todd Blanchard wrote:
>> I like the rails mechanism for specifying page layouts (boilerplate
>> template that surrounds the currently rendered view).
>>
>> Its simple and obvious.
>
> Use the "extends" tag. If you want rails style boilerplate, there's
> always "include"
>
> http://docs.djangoproject.com/en/dev/topics/templates/#template-inheritance
> --
> Andy McKay
> @clearwind
> Training: http://clearwind.ca/training/
> Zen: http://djangozen.com
>
> --
>
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django-us...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=.
>
>
>
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=.
