From af83b650be6668e30a017941048302f17100ad03 Mon Sep 17 00:00:00 2001
From: Malcolm Tredinnick <malcolm.tredinnick@gmail.com>
Date: Tue, 26 Aug 2008 07:11:14 +0000
Subject: [PATCH] Fixed #8150 -- Updated a reference to creating an admin class
in the overview document. Based on a patch from mk.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@8574 bcc190cf-cafb-0310-a4f2-bffc1f526a37
---
docs/intro/overview.txt | 14 ++++++++++++--
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/docs/intro/overview.txt b/docs/intro/overview.txt
index 79ce653106..b505369f37 100644
--- a/docs/intro/overview.txt
+++ b/docs/intro/overview.txt
@@ -133,7 +133,11 @@ A dynamic admin interface: it's not just scaffolding -- it's the whole house
Once your models are defined, Django can automatically create a professional,
production ready :ref:`administrative interface <ref-contrib-admin>` -- a Web
site that lets authenticated users add, change and delete objects. It's as easy
-as adding a line of code to your model classes::
+as registering your model in the admin site::
+
+ # In models.py...
+
+ from django.db import models
class Article(models.Model):
pub_date = models.DateTimeField()
@@ -141,7 +145,13 @@ as adding a line of code to your model classes::
content = models.TextField()
reporter = models.ForeignKey(Reporter)
- class Admin: pass
+
+ # In admin.py in the same directory...
+
+ import models
+ from django.contrib import admin
+
+ admin.site.register(models.Article)
The philosophy here is that your site is edited by a staff, or a client, or
maybe just you -- and you don't want to have to deal with creating backend