Well, it appears to me we still somewhat disagree about the nature of use case for admin site—IMO not only Django admin is a data browser, but also a rarely nee

Well, it appears to me we still somewhat disagree about the nature of use case for admin site—IMO not only Django admin is a data browser, but also a rarely needed one. Admin staff should only have to access it when looking into some problem. In that case lack of view mode probably wouldn't matter much, and fixing other minor inconveniences may not be worth it. Meanwhile, if there's some ‘legitimate’ use case involving browsing your data—well, Django makes building a dedicated UI for that quick and easy enough. Take class-based list/detail views[0], throw in a couple of templates, and you're done—and the result is easier to customize than the admin site. This, of course, depends on a project—the amount of maintenance involved, possibility of change in requirements, and other factors. [0] By the way, class-based view documentation got a neat update recently, now easier to read and navigate: https://docs.djangoproject.com/en/dev/ref/class-based-views/ https://docs.djangoproject.com/en/dev/ref/class-based-views/