News for hackers. Stuff that matters.
Re:Django REST framework 3.7 released by theli0nheart on Wednesday November 01, 2017 @09:16PM (#15607068)
> * Adding a link to a custom page onto the frontpage of the admin, ideally under a custom "App" header.

This one's simple—just override base_site.html.

As for the others, I'm not really sure I understand what creating a read-only view / form for nested 1-1 objects means, but I'm sure there's a decent, not so crazy solution out there.

Re:Django REST framework 3.7 released by Alex3917 on Wednesday November 01, 2017 @10:29PM (#15607370)
> just override base_site.html

And if your changes break in a future version of Django, how exactly is anyone going to be able to debug that? Having to override admin templates that are at best only semi-documented is incredibly hacky.

Re:Django REST framework 3.7 released by theli0nheart on Wednesday November 01, 2017 @10:40PM (#15607425)
With any Django app, you’re going to pin your requirements to a specific Django version as a matter of course. If the change is broken in a future Django version, you’d need to update it like you would need with any other breaking change.

But, if experience is any guide, despite lots of tinkering with the admin, Django has yet to break anything I’ve customized in the admin (I’ve been using Django since 0.96). YMMV.

Re:Django REST framework 3.7 released by Daishiman on Friday November 03, 2017 @02:54AM (#15617146)
Django has the best deprecation policy of any framework I've seen. Breaking changes are always documented and given fair advance for changes.

In many years of working with Django I have not really seen a significant breaking change in the admin unless you override private methods.