Stefan Bethke writes:
I understand. Would you be open to some documentation about the general approach and a few pointers in the right direction? For people who are not familiar with Django this is not very obvious.
Yes, Without seeing your contribution, I think something like what I wrote with a more precise pointer to Django documentation on overriding templates would be optimal. But I would be open to suggestions.
And also, would you accept a change that enables replacing the icon in the nav bar and (extending/replacing) the footer, by defining a block each for these places with the current content as the default?
I would have to see the proposed change. As I said before, I am generally opposed to making it easier to replace our branding. Making the footer extensible while preserving our branding would be fine with me, but it seems to me that it would be hard to do that in a way that would satisfy most use cases and be reliably attractive.
My rationale is that I do not want to track changes to postorius/base.html manually,
Yeah, I understand that. Still I'm reluctant to approve it (espcially sight unseen), but I won't veto it, or any of the parts you've mentioned. So I recommend you consult Abhilash Raj <maxking@asynchronous.in>, who is the committer most recently active on Postorius as far as I know, specifically base.html.
-- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan