Ticket #12811: 12811_tutorial_patch.diff

docs/intro/tutorial02.txt

@@ -447 +447 @@
 make significant changes to the layout. After all, the index is probably the
 most important page of the admin, and it should be easy to use.
 
-The template to customize is ``admin/index.html``. (Do the same as with
-``admin/base_site.html`` in the previous section -- copy it from the default
-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
-installed Django app. Instead of using that, you can hard-code links to
-object-specific admin pages in whatever way you think is best.
+The template to customize is ``admin/index.html``. As with
+``admin/base_site.html`` in the previous section you don't want to edit the 
+original file. Instead, copy it from the default directory to your custom 
+template directory, then edit the copy.
 
+In that file, you'll see a reference to ``{% for app in app_list %}``. This is 
+Django's way of iterating over a variable named ``app_list`` which contains 
+every Django app in :setting:`INSTALLED_APPS`. The index page is normally 
+created by iterating through those apps and creating sections for each one
+automatically. You can override this behavior using Django's templating 
+language, but we'll talk more about that in the next 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.