core-admin VS django-admin-interface

Like most things, it's probably a combination of things.

The Django Admin existed before Django publicly existed. That meant that once anyone started using Django they knew that they should constrain their use of Django in certain ways so that the Django Admin would work with their usage. Features that would be added to Django would be built with the Django Admin in mind.

Many tools like Flask or FastAPI don't have an opinionated model layer like Django. Without that, you can't really create an admin interface programatically. People could be storing their data in any sort of fashion anywhere. How would one build an admin system for something like Flask or FastAPI where there's no convention around how people set up data access? A lot of frameworks out there don't tell you "access your data in this way" or "this is how users will be authenticated." Without those two things, it's hard to really create an admin system.

There are similar systems available for some frameworks, but since they aren't part of the core framework, they don't get the same attention. Someone creates it, but it doesn't have the kind of community buy-in that sustains it. One of the odd things about Django is that the admin system is under `django.contrib` which indicated that they didn't intend for it to be in the core of Django forever, but that's not really how `django.contrib` ended up. It continued to be a core part of Django maintained as part of the framework.

Like I said, there are admin dashboards available in other frameworks like RailsAdmin (https://github.com/railsadminteam/rails_admin) or Core Admin for .NET (https://github.com/edandersen/core-admin) and I'm sure there's more. However, both Rails and .NET provide most of what Django provides (and a lot more than most frameworks). Rails and .NET both have a default data access ORM that a majority of people using those frameworks tend to use. .NET has built-in authentication/authorization so the admin can work off that. Rails doesn't have auth, but RailsAdmin uses some plugins.

If CRUD only is your goal, there are existing out of the box options such as this: https://github.com/edandersen/core-admin

There are projects in other languages/frameworks like .NET (https://github.com/edandersen/core-admin, https://github.com/serenity-is/Serenity), but nothing quite has the momentum that the Django admin has.

There's a good plugin called django-admin-interface that cleans up the Admin page to a point where it is still recognizable as the admin page but looks nicer. You also can customize the color themes, matching the palette of the app.

https://github.com/fabiocaccamo/django-admin-interface

When I started to use django more than 10 years ago, I was really happy for the admin, immediately after I felt the necessity to customise (re-brand) it for each client, so I looked for available packages and my conclusion was that all admin replacements in the end become hard to maintain, have many issues open and are abandoned, so I ended up writing my own solution that does exactly what I needed: customise the interface using the admin itself. Many years later my solution still works and have few issues open, I use it on a daily basis on different projects and many other users use it. This package is publicly available on GitHub/PyPi: django-admin-interface (I’m the author, any feedback is appreciated).

I’m the author of django-admin-interface, it is actively maintained, well tested and appreciated by the community (more than 1k stars), give a look at it! ;)

Sure, I published and maintain many django packages, the most appreciated one (more than 1k stars) is django-admin-interface.

I've been using django admin interface and it's great. Really well written. https://github.com/fabiocaccamo/django-admin-interface