Lists like these are all well and fine, but there's almost certainly something you can do about them in Django. You can make third party apps that do what you want, it's the best way to prove that it's possible, and to make forward motion, and to scratch your own itch, and to see if people like it. I don't find much value at all in airing grievances about minor annoyances in OSS.<p>#1. The default ModelAdmin can not, This is totally true. You could overwrite every applicable method until it does for a specific set of models, though I'd gather that this is more trouble than it's worth.<p>#2. You can restrict permissions to staff members that are not superusers. You do this via the permissions system, either the built-in one or the custom one. It's true that in the default admin.site, staff members can access the index page, but the index page may be empty for them.<p>#3. With the proper permissions, modules or models are hidden from that user. django-admin-tools gets you the rest of the way to that goal.<p>#4. There are workarounds as you note, they almost all would require some concession on more third-party libraries in the core, or the possibility of linking a 15MB image to a page.<p>#5. Solution Noted :)<p>#6. You could probably subclass ModelAdmin to fix this one. I'd like to see it done, though personally I don't see it as a big deal.<p>#7. I don't like GFKs, I don't have any strong opinion on their widgets or what could be better, You could make a very detailed widget presumably though<p>#8. This isn't entirely true, you can use inlines. You could probably hack the normal widgets too to give you an edit button with ?popup=True (not positive about that)