Context Navigation

Changes between Initial Version and Version 1 of Ticket #18665, comment 3

initial	v1
1	1	Sounds good to me on #3 and #4, I'll make those separate tickets.
2	2
3		As for the problem with AdminPlus is if I'm writing a reusable app and other use it. If I wanted to add custom views to say my django-app-metrics project, I can get the URLs mapped to views no problem, but I can't display the links without forcing the user to use a sub-class of Admin.site or messing with the templates. Add in another app that might want to do the same thing and you likely cannot have both at the same time working.
	3	As for the problem with AdminPlus is if I'm writing a reusable app and others use it. If I wanted to add custom views to say my django-app-metrics project, I can get the URLs mapped to views no problem, but I can't display the links without forcing the user to use a sub-class of Admin.site or messing with the templates. Add in another app that might want to do the same thing and you likely cannot have both at the same time working.
4	4
5	5	I'm not looking to add another name next to AdminSite, ModelAdmin, etc. but instead buil this functionality into them so they can be picked up, detected, and rendered using the normal means. Akin to list_display for ModelAdmins and perhaps a concept of a "AppAdmin" or other standardized way of discovering app level links/views for applications that do not have models. Definitely open to suggestions!