Django-Admin-Deux: From First Steps to Custom Plugins
Published October 26, 2026
This video features Emma Delescolle at DjangoCon Europe 2026 in Athens, Greece.
TALK: Is it time for a Django Admin rewrite? If so, how? by Emma Delescolle
What if customizing Django's admin felt like writing any other Django view? Not just a cosmetic refresh, but a radically new approach relying on Django itself, factory-generated views and with a plugin-first design.
More information: https://2026.djangocon.eu/speakers/XREAEA/
Follow DjangoCon Europe on social media:
*X - https://x.com/DjangoConEurope/
*LinkedIn - https://www.linkedin.com/company/djangocon-europe/
*Mastodon - https://fosstodon.org/@djangoconeurope
#django #djangocon #djangoconeurope #djangoconeurope2026
Automatically transcribed, so expect mistakes in names and technical terms.
Speaker 1: Okay, um I think we can all agree that the Django admin is something that is rather old by standards from nowadays and stuff got bolted on bolted on all the time and maybe it's time for a complete rewrite. Emma is going to tell us more about this. She's currently a steering council member, hopefully for the next release cycle as well, but we will see about that. Give her a warm welcome.
Speaker 2: Hello. So yes, my name is Emma. My main claim to fame right now is being part of the Django Steering Council. I also run a small company in Belgium that's called Lavit. and we do a lot of uh Django development. I also work with uh squads which is uh a grouping of uh consultants mostly senior consultants and you can hire a team and only pay what you need and I go through them for larger projects And we all love Django. This is why we're here, right? If if somebody doesn't love Django, maybe you're in the wrong conference. But I I do love Django.
Speaker 2: It's a great web framework. The tagline is web framework for perfectionist with deadline. It's 20 years old, almost 21 now. It's got a bunch of features out of the box. A lot of batteries are included. And one of the included batteries is the Django admin. The Django admin is one of the things that when you have never seen it, when you see it for the first time It makes you go whoa this this is comes free with Django you you get all these features this is great And uh I mean there is uh a saying that come to Django for the admin
Speaker 2: stay for the community. Have have you heard that before? Uh I I've certainly heard it and yes, the admin is one of the many things that drew me to Django. Um the the the admin is really good. In only four lines of code you have a full credit interface with authentication, authorization , you have filtering, you have searching, you have Probably for uh if you're doing some sort of uh enterprise back office or ERP or well your job 80% is going to be CRUD plus a little something and here you already have the cred
Speaker 2: plus search filtering and all that. So yeah, that that that that's great. Um now of course the the the plus in in crut plus uh sometimes You need things that are not native to to Django or to the Django admin. But uh in Django, there are third-party applications. That's that's the secret source of Django. So let's let let's use third party application. You you need some some drag and drop uh in in a list in the admin There is a package for that. I I I can see the the author of that package um i in the front row. So yeah, let's
Speaker 2: let's put some heavy cream in ourselves and let's start off source. Then I I will also like little stuff like uh custom actions displayed on each row of the of of the admin. That's that's another thing that's got a package and yeah let's Let's put a bit of salt in there. And now I I want also to to have uh nested inlines. There's also a third-party app for that. Let's Let's add some garlic in there. And no, I would also like to customize my forms. I would like to my forms to be just two columns, all by forms. I just want them to be two columns. Yeah, let's let's add a bit of of lime juice in there.
Speaker 2: And yeah, I I also want you to customize some of the aspects. Um so uh maybe I I want some translatable models. Yeah the translatable models I live in Belgium. We have three official languages. So translatable models is something I need. Yeah, let's put some more ingredients in the sauce. Let's add some strawberry jam. If you've ever tried to make yourself something to eat and you've paid attention to all the ingredients that that I've listed right now. You're policing this this is all coming apart. This is going to be disgusting. And uh unfortunately that's that's also what happens when you're trying to add too many third-party
Speaker 2: applications to to your Django admin. Some will clash with each other, they are not going to be compatible. So you might want to to try and do it yourself. and you will be meeting the change list view, the change form view, and those are hard to extend. And there there is a reason uh why they're hard to extend. Um the truth is that the admin was not really built for Django. Django was built around the admin that was uh developed as a need for newspaper and the admin predates The admin itself redes most of Django.
Speaker 2: Django is 20 years old. The admin is as old as that. And for some reason some people uh have always had harder time to get into adding features for the for the admin. So the admin is a bit stagnated while Django itself was uh getting some newer features, some newer um practices the admin still was improving but more slowly. The fact is that a lot of the good practices that we use in Python today did not even exist when the the Django admin was written. If you think of things like data classes, they did not exist and there is no
Speaker 2: not a single data class in the code for the Django admin. Uh enums. I found one enum in uh the the Django enim code because Well, it was not a tank when the wiki admin was written and you don't you usually don't go through the existing code to rewrite it with new features. You just keep using it until it breaks. Things that you might be more familiar with, like F-strings. Only half of the string manipulation in D Django admin is done with F-strings. Um and the the what we're coming at is that really Django is a framework And the Django admin
Speaker 2: is a framework inside the framework that doesn't really work like the rest of the framework. And documenty knows about it. I've talked to several of you. You told me of things that you're trying to do. Last year we launched the new features repo on GitHub. And last time I checked about a third of the new features requests were for the admin. Which when you think that the Yanmin is only a small bit of Django, this is this is huge. Um I have not followed up but I know that there has been talks of uh frontend group that wants to uh reskin
Speaker 2: the admin. And there's also on the new features repro issue issue seventy that's just says free thank the admin. So that's the community knows. And not only the community knows, but the the community has been trying to fixed things somehow for the past fifteen years at least. My favorite attempt to of doing that was Django Admin 2, which which was based on factories using the Django generic views. Because the the admin has all this code to do CRUD, but beside that Django itself has all this code to do
Speaker 2: code. There are the list the generic views and so we're maintaining two different versions of that. So Django had me into tried uh to to take advantage of that. And it it was a good project. Unfortunately it's been abandoned because the the maintainer moved on to something else Then there are tools like Grapelli and Jet. As far as I know, Grapelli is the oldest try at re-implementing the admin somehow. Grappily and Jet are mostly skins or templating over the admin, but they also add a few little bits. Then there are things like Wagtail. Wagtail, which is one of the major CMSs for Django, has its own admin
Speaker 2: that is not Django admin. And some pay some people are just taking out the the wagtail part out of the wagtail admin and are using uh the wagtail admin for regular Django projects Um I have given my own try at this. I have uh published the RF uh schema adapter, which uh lets you use uh Django Rest framework uh to build um an API and then export that automatically to a um JavaScript front end. And I 'm still using that today. It's starting to look a bit dated though But uh I I I'm still using that and it still works great.
Speaker 2: And um So if we looked at at things, I said that's with the Django admin you want to go you you go whoa when you see it first. And twenty years ago, uh Django admin was mostly the only one that was doing that. There was Rails that had a very different approach. Rails uses um blueprints and um you write there is a lot of code that's automatically generated for you. Django uses uh inheritance instead and there is no code generated for you. You you write all your code. And for about ten years, um
Speaker 2: those two were your only choices if you wanted something that was quite capable out of the box. But yeah, then other frameworks got up. And starting five years ago, not only have other frameworks caught up, but they started shipping with things that are not part of Django. Not part of Django, I mean you have things like live wire or turbo. that uh adds some uh dynamic uh features to uh the admin interface of Laravel and Rails There is HTMX, there is uh filmed, there is all that. And there are some packages for Django that are trying to uh to bring those to Django
Speaker 2: Um I mentioned the Wagtail admin, uh there's also Jet. Uh they all bring in a beautiful uh UI, but they also add a few tools to to make uh the admin more polished. And one thing about those tools is also that they are very opinionated. Django used to be more opinionated than it is now. And these tools somehow are trying to to put that back. So what what does the future look like for um for a Django admin? Well we can look around and see what the others do. We can also see what they don't do well and try to do better. And my take on it is that uh
Speaker 2: an admin should be extendable, composable. uh Django native and pluggable. Um but most importantly The admin should be Django and just Django. It should not be something else that you have to learn on top of Django. And if you write something for your admin, you should be able to at some point say, oh, I don't want this in the admin after well, I want it outside of the admin and just move it out and use it outside of the admin. So what if your admin was just Django code? Um there's a lot of things that we can use directly in Django. I mentioned there's generic fields that do
Speaker 2: a lot of what you want to do when you do CRUD. There is the generic list view, there's the generic update view, the generic uh delete view and the generic create view. So that's that's all cred and and we we we have that. But um I also want Things to be composable, not only views, but also things like permissions and things like that. We we just had a talk about uh authorization for very complex cases, uh and we have solutions for that. But there's also a lot of more simple cases that uh Django does not provide things for. There are other packages in Django that provide that. Django Rest framework, for example, has these permission classes that are uh authenticated
Speaker 2: uh write access and read-only uh to everybody. That's um that's just one example. And to avoid the clash when you're trying to compose something right now, as we mentioned, when you're trying to add too many third-party applications. The admin was not really built at the start to to accept to have third-party packages. It's something that has been crafting itself onto it. There's a lot of those packages that need to override things like like template and things like that. So if we could have something that has been designed plug-in first in mind, that would be great. But once again
Speaker 2: The most important, and I'm not going to repeat that enough, is to be able to use familiar pattern and not have to um to re to to relearn a different framework when you go in and out of the admin So what would the architecture look like? Well it would be based on the the generic views that Django provides On top of that, we can build a UI layer. It's a matter of just providing a few templates that any view can find. We mentioned things that are not graphics related, so that are not visuals, things like permissions.
Speaker 2: And here I'm going to start talking about action. So if you hadn't guessed yet, I did write a proof of concept for a new admin. And um I found out that At some point I needed something to hold the recipe for every uh view that I wanted uh to have. And I've been calling those actions. So an action says, hey, I have a view and my view is going to be based on a list view. um and is going to need those permissions. That's that's the freely base of the of the action Um and then on top of that, so that this can be extensible and composable, we we need a plugin
Speaker 2: system Simon Willison uh wrote DJP, which is a plugin system based on plug-y, and I have used that as a base. And so the action is a great place for the plugin system to say, oh, hi, uh, I am a plugin. And uh for every um list action, I would like to register a mixing and I would like to add search capabilities, for example And to bring all that together you need a bit of glue and a bit of glue is in this case the same um the same concept as in the base uh Django admin 2 which was uh
Speaker 2: view factory that just built uh the view the final view class on demand from what the code you have defined and the plugins that you have installed. And remember, this is how the Django admin works right now. This is how you define an admin, a model admin. And this is straightforward, this is clear, this is easy. This is something that we should absolutely keep. So this is what the same admin looks like in Django Admin 2. Uh did you spot the difference? The only difference between the two
Speaker 2: is the imports. Everything that you have already learned for Django admin works in in the new Django admin 2 or Django admin duo. The Django admin 2 package name was already taken. I had to find something else. So this is Django admin 2 But once you have done the steps of changing those imports, Django Admin Do also unlocks a few features. things that I've heard a lot of you mention things that they they needed. So like for example for List display instead of just giving the field name I can give a column object that has the field name but has more information like is it sortable is it filterable
Speaker 2: um for my forms instead of just having uh field sets I can have a layout object layout object that can have many uh things in that and uh the the the factory will just take all those information and build uh something with it. So it's it's nice to to mention features but maybe it's it's better to to to see it in action Um this should autoplay. This does not autoplay. How do I autoplay? Oh how do I play on that? Okay. Um so this
Speaker 2: this might look like uh just a skin on a Django admin, but it's just it's an entirely different package. It's Django admin du. And it works. It provides the same features. Some of the features of the admin right now. It doesn't provide all the features of the admin. So you can see here basic uh usage uh you can edit uh things that like this is this is something that that you would expect. Right now this is uh light mode Not only it is in light mode because it's a white background but light mode also as in it's just Django admin 2 with nothing else included So you you you might have seen already the there was an extra button there in the list.
Speaker 2: There was change password for users. This is uh a new action that you can plug in and it works out of the box in Django Admin Do. You you have users, you have a specific view just to change the password, well this can be this can appear directly in the list. Now of course everything else works. And if you look here you see that in form view you also have access to this action, for example. This uh this is a is a small thing, but this shows that this is the uh this is the regular features do work, the best features that you would expect do work In a bit we're going to be moving to dark mode.
Speaker 2: And in dark mode, this is not going to be just Django admin du. This is going to be Django admin du with recommended plugins. So you might have you might notice here that we we have the basic features but uh and we have uh two fields. Uh we can have uh multiple fields, multiple columns in the form and things like that But uh we don't have more advanced things like search and filtering. Um search and filtering come provided by plugin. There is a plugin that uses Django filters to uh to to add plug uh to add uh filtering capability as well as sorting. Uh search is out of the box You have also advanced form
Speaker 2: features that are not available straight out of the box in Django Admin Dov, but you have a plugin for Django Form Set. Django Forms Set is a package that lets you have very complex and full featured Django Forms. So this here uses Django form set. You might not have noticed much difference between the form in the light mode and the dark mode. And that's on purpose, but it's a whole different library using a whole different different uh base view that uh manages the forms here and it's uh Django form set that will allow you to do things like uh conditional display fields or uh nested in lines out of the box.
Speaker 2: So here we also can notice see that we have two uh different widgets on the sidebar Those are provided by different plugins, but they work together. I am using search and filter uh right now at the same time and uh both uh work together. But with this plugin architecture, I might get lost in my code. What plugin defines what? Is there a mix in there something? So another plugin that is provided is um adminDo Classy Docs that will uh generate CCBV style documentation. Um
Speaker 2: And uh so you can see uh very clearly what is defined by what plugin, you can explore the code. Um uh you you can really you don't have any surprise and see how how come my view is doing that well you can go in the documentation you see the you see the method you see what declares the method there is nothing hidden But that's that's good, that's good, it works. How how can we know this is robust? How can we know this is not going to break? Well, the best way to know that is to try to break things. And so I did that. Um last year I released uh Django Rest
Speaker 2: 2. Which is a small uh REST package that allows you to do REST with only uh Django code. And so I did a Django Admin the plugin for REST 2. And this is this is the result. This is a front-end JavaScript application that talks to the REST backend. that you just saw and yeah it just works. Uh didn't break anything. So I I think this this is clearly a sign that things are are robust Um there are already a list of plugins that work. I'm giving a workshop tomorrow. If you want to know more about those plugins, come to the workshop.
Speaker 2: You can trade without any risk because admin 2 works outside of the admin. It can work in parallel. So if you want to give it a try for a specific model, use something that you cannot do in the admin. trade outside and do progressive enhancement. A lot of things do will not require a lot of effort to migrate. There are things that will require absolutely no effort because either they will be provided directly in Django admin or it's uh third party applications that don't do anything with the admin. And then there was gradual tiers of effort. What is going to be the hardest to integrate with Django Adminder
Speaker 2: is that if you are modifying the templates or the view, the change view uh with your third-party application, that's going to be the hardest to integrate. But uh if um all you do is add an action to the admin like Django import export, that's not going to be too much work. So what's the roadmap for this? Well this probably at least nine months uh to to to keep working on the core plugin And then there's uh probably six to nine months to try to collect uh data, information from third-party applications
Speaker 2: and make sure that All the well-known and most popular third-party applications can work correctly with this kind of architecture. And then if this goes i if this keeps falling, there is a big work of community work. to be able to support everybody who would want to migrate to Django admin. It's not just, hey, here's something, a new package is a new admin. No. Do whatever you want with it. We are going to need to support that and we are going to need to help the users. And this brings me to the core of it. Everything in open source we're always saying, hey, we need more funding.
Speaker 2: Ten years ago Jacob Kepler Moss said that it would take about a million dollars to rewrite the admin. I do not have that kind of money. Um but there are some solutions for that. There's uh things like the server integrants or NLNet who uh grants will give grants to open source uh to maintain or uh bring new features. So currently I'm waiting to hear back from NLnet for a grant application I put in there. Uh once I have their reply I will also put in a grant application for uh the German sovereign tech fund But uh your company you you can also if if you're saying oh this is something that I I would like to use
Speaker 2: you can also uh sponsor the project by asking me to help you integrate Django Admin 2 , adding some features that you need for your own project. This uh will contribute to the project. If you just want to send me money, you can too. But so what can c what could come next? Well we just saw in the previous talk that permissions are a big thing So more permissions integration with uh either stock guardian or the authentic uh guardian. Um Better support for related model operations. This is currently a bit lacking in and in the internationalization.
Speaker 2: I have spent no time on that. uh definitely more teams and maybe who knows your project in any case this needs you Please try it, give feedback, install it, come to the workshop tomorrow to have a more detailed look at the project and see how this can solve your problems. And uh thank you. I think we may still have a bit of time for questions.
Speaker 1: Well amazing, thank you. Uh we do indeed have time for questions. And I guess there will be many, so we will do two or three and then ask her at lunch break or afterwards. So questions, anyone? No take us.
Speaker 3: Yeah, hey, thanks Emma. That was amazing. Thank you. I have a question about the the look of the admin. Uh why doesn't it simply look like the old admin?
Speaker 2: Because I wanted it to look familiar, but uh teams are our plugins as everything else. The core of Django Admin is a plugin itself. So if you want uh to change the theme, you're more than welcome to do that. I've tried so far to use mostly semantic HTML. I've stayed away of from classes where I could. So it should be pretty easy to skin it, but since this is still a project in an early stage If you start working on a theme today you should expect things to break and have to keep working at it. But uh
Speaker 2: theming uh is a plug-in like any other functionality in in the admin and so If you don't like it, you can change it.
Speaker 1: Okay, we've got another question upstairs.
Speaker 4: Uh hi, thanks. Imagine that we want to to use uh something like server send events, maybe with signals, so that people looking at the admin uh got you know live updates. Is this something that would be possible or
Speaker 2: yes there's something that would be possible um HTMX and dynamic page and receiving events and things like that was something that was on my mind uh since I started working on this project. Plugins may register uh front-end elements for uh different uh view types, and so uh they can also register media like CSS, JS, and so on. And so what you would want to do is probably register, have a plugin that registers some uh JavaScript and maybe uh a zone uh on the screen to be able to uh show notifications or whatever you want to do with those events.
Speaker 1: So one last question and then some small announcements.
Speaker 5: Uh hi, I also think this is amazing. I wanted to ask you if you tried m uh multi-widgets for fields because maybe I missed it in the demo. For example, OSM widget or daytime picker, how does it handle those widgets? from original Django admin?
Speaker 2: So um here there are two different things. So there is the the the simple Django admin duo that's uh doesn't do uh anything that Django doesn't do You can still customize it's still a Django form behind it, so you can we you can customize the widget if you want. But if you really want really nice forms and a lot of alternative widgets, I would uh strongly encourage to using the uh plugin that uses Django Fromset. Django FromSet comes with uh many uh very uh polished widgets for a lot of things
Speaker 1: Okay, thank you for the great talk and another round of applause.
April 15 - 17, 2026
Athens, Greece
Note: We understand that names change, people change, and bodies change. We respect each individual's journey and privacy. If you have any concerns about a video or need us to remove content, please don't hesitate to contact us. We will handle your request with care and promptly address any issues.
Published October 26, 2026
Published October 26, 2026
Published October 26, 2026
Published October 26, 2026
Published October 26, 2026
Published October 26, 2026