.
, where each site can have its registered models, apps, admin views, etc.. ok?
Those different admin sites are limited to one interface/html structure, located at `tempates/admin`. A change in one admin site base.html will affect the other admin sites.
Proposal:A way to direct each AdminSite to the template path where it should find the templates.
Example:
Add a setting called ADMIN_DEFAULT_THEME = 'admin'
Add an attribute to AdminSite called theme which default to ADMIN_DEFAULT_THEME, and basically this setting controls which directory this admin site look for templates.
So whenever a path like 'admin/some_file_name.html' occurs, it is to be replaced with something like f'{admin_theme}/some_file_name.html'
This will take effect in extends statements, AdminSite templates loading(index/app index / etc) and ModelAdmin template loading (change form/list/delete etc..)
Final thoughts:
* I see no real reason why we should not implement this.
* I sits well with the multi admin site idea. If we can have several different sites then they should be able to look different .
* This open the door for admin theme to be something plug and play which in my opinion have some interesting nice outcomes
Finally, Thank you for your time reading this and i hope you support it or engage in a discussion.
Looking forward for your replies ..