Gain insights into the Django Admin interface, learn about automatic generation, data management, custom functionalities, advanced UI customization, and explore admin rights permission management.

The Django Admin Ultimate Guide_Stripe API Integration copy.png

Django.tar.gz

django

django-lesson1

django-faker

django-rebranding

django-user-management

django-rebranding-changelist

django-migrations

django-add-view-index

empty

django-rebranding-old

In this course, you will learn the basics of the Django Admin interface, a great tool to build a powerful admin interface quickly for your Django project. 

First, you will learn how to automatically generate the admin interface for your Django models, how to populate fake data, and then search or filter data with some advice to improve performance. 

Next, you will see how to extend the functionalities of the admin interface such as adding custom fields, add intermediate pages, or creating custom actions like exporting data in CSV format.

After that, you will also explore basic and advanced UI customization such as adding charts or modifying the index page.Finally, you will have a look at the Django admin rights permission management.

The Django Admin for Web Developers

# Adding custom fields

So far you have seen that you can use `list_display` to display model fields in the list page of the admin. But it is also possible to display a custom field that does not exist in the model.

For instance, if you want to display a new field in a new column to indicate that a question has been published or will be published in the future, you can create a `has_been_published` function inside the `QuestionAdmin` class and also add this property to the `list_display` list:

```python
list_display = ('question_text', 'refAuthor', 'has_been_published', 'pub_date', 'createdDate', 'updatedDate',)
list_display_links = ('question_text', 'refAuthor',)

def has_been_published(self, obj):
	present = datetime.now()
	return obj.pub_date.date() < present.date()
```
The new `has_been_published` field has been added in the `list_display` and its value is being calculated within the function: `has_been_published(self, obj)`. This is how it works: You need to define a function with the name of your new field added and passing the parameters `self` and `obj` (which represents the instance of the model).

If you go to your question list page in your admin, you can see the new column `has_been_published` with a value of `True` or `False`.

Learn how to add custom fields and custom links.

Getting Started

Design Customization

Advanced Customization

Access and Rights Management

Conclusion

Custom Fields

Adding custom fields