I suggest you use the
- extends template
- base.html
- the conventional title, extrahead, content_title, content, etc. blocks
combo from for the polls tutorial from the start when the template
language is first used in
https://docs.djangoproject.com/en/1.4/intro/tutorial03/
since this is an absolutely fundamental design pattern.
While the "do simple now and improve later" strategy could be used (in
tutorial 5, we say: wow, lets refactor some more code!), I think the
direct approach is better here, since it is pretty obvious that this
factors out the code.
--
Ticket URL: <https://code.djangoproject.com/ticket/19106>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
* type: Uncategorized => New feature
* stage: Unreviewed => Someday/Maybe
Comment:
I disagree - the "simple and improve later" is a much better idea.
It's easy to explain simple things. Once the basics have been grasped, you
can extend and provide more complexity. If you introduce the complexity
early, you have to say "just do this, and ignore the reasons why", which
leads to cargo-culting.
So - marking this ticket as someday/maybe, for the purposes of introducing
a new tutorial step on template blocking.
--
Ticket URL: <https://code.djangoproject.com/ticket/19106#comment:1>
Comment (by mattseymour):
I agree completely with @russellm comment. Could the tutorials maybe
include an end of section "Something to look at next" where we could list
some simple improvements or additional features the user could attempt?
This section would purely be additional reading / features the user could
add it without conflicting with the tutorials in anyway.
--
Ticket URL: <https://code.djangoproject.com/ticket/19106#comment:2>
Comment (by timgraham):
Also raised in #26501. My comment from there:
In general, I think it's difficult for apps to provide sufficiently
generic templates that will integrate into a site's layout. Some have
proposed some [https://django-reusable-app-
docs.readthedocs.org/en/latest/apps/templates.html common conventions]
that may work to some extent but in my opinion trying to provide reusable
templates shouldn't be a big emphasis of reusable apps.
--
Ticket URL: <https://code.djangoproject.com/ticket/19106#comment:3>