p15693087
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixed #12811 -- Modified Tutorial 2 to indicate that the templating language will be covered later. Thanks to bac for the suggestion, and Gabriel Hurley for the draft text. 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@12710 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Russell Keith-Magee 2010-03-08 03:19:57 +00:00
parent b50a35a669
commit 36e97e59cd
1 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/intro/tutorial02.txt
View File

@ -425,6 +425,13 @@ above, then copy ``django/contrib/admin/templates/admin/base_site.html`` to
Then, just edit the file and replace the generic Django text with your own Then, just edit the file and replace the generic Django text with your own
site's name as you see fit. site's name as you see fit.
This template file contains lots of text like ``{% block branding %}``
and ``{{ title }}. The ``{%`` and ``{{`` tags are part of Django's
template language. When Django renders ``admin/base_site.html``, this
template language will be evaluated to produce the final HTML page.
Don't worry if you can't make any sense of the template right now --
we'll delve into Django's templating language in Tutorial 3.
Note that any of Django's default admin templates can be overridden. To Note that any of Django's default admin templates can be overridden. To
override a template, just do the same thing you did with ``base_site.html`` -- override a template, just do the same thing you did with ``base_site.html`` --
copy it from the default directory into your custom directory, and make copy it from the default directory into your custom directory, and make
@ -452,7 +459,9 @@ The template to customize is ``admin/index.html``. (Do the same as with
directory to your custom template directory.) Edit the file, and you'll see it directory to your custom template directory.) Edit the file, and you'll see it
uses a template variable called ``app_list``. That variable contains every uses a template variable called ``app_list``. That variable contains every
installed Django app. Instead of using that, you can hard-code links to installed Django app. Instead of using that, you can hard-code links to
object-specific admin pages in whatever way you think is best. object-specific admin pages in whatever way you think is best. Again,
don't worry if you can't understand the template language -- we'll cover that
in more detail in Tutorial 3.
When you're comfortable with the admin site, read :ref:`part 3 of this tutorial When you're comfortable with the admin site, read :ref:`part 3 of this tutorial
<intro-tutorial03>` to start working on public poll views. <intro-tutorial03>` to start working on public poll views.