Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

Fixed #9236 -- Added documentation on the dependencies of the admin.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@11543 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
commit ec6b9d6e63cc352052e6a4c4d36d67f6656c43b7 1 parent 27c6821
Russell Keith-Magee freakboy3742 authored
Showing with 10 additions and 5 deletions.
  1. +10 −5 docs/ref/contrib/admin/index.txt
15 docs/ref/contrib/admin/index.txt
View
@@ -27,19 +27,24 @@ Overview
There are five steps in activating the Django admin site:
- 1. Add ``django.contrib.admin`` to your ``INSTALLED_APPS`` setting.
+ 1. Add :class:``django.contrib.admin`` to your :setting:``INSTALLED_APPS``
+ setting.
- 2. Determine which of your application's models should be editable in the
+ 2. Admin has two dependencies - :class:``django.contrib.auth`` and
+ :class:``django.contrib.contenttypes``. If these applications are not
+ in your :setting:``INSTALLED_APPS`` list, add them.
+
+ 3. Determine which of your application's models should be editable in the
admin interface.
- 3. For each of those models, optionally create a ``ModelAdmin`` class that
+ 4. For each of those models, optionally create a ``ModelAdmin`` class that
encapsulates the customized admin functionality and options for that
particular model.
- 4. Instantiate an ``AdminSite`` and tell it about each of your models and
+ 5. Instantiate an ``AdminSite`` and tell it about each of your models and
``ModelAdmin`` classes.
- 5. Hook the ``AdminSite`` instance into your URLconf.
+ 6. Hook the ``AdminSite`` instance into your URLconf.
Other topics
------------
Please sign in to comment.
Something went wrong with that request. Please try again.