Mark Sapiro writes:
 > On 9/22/25 05:21, Wikinaut wrote:
 > > Mark, this is great news, a little bit like expected!
 > > Thanks again for clarifying the term "generic" here. It's helpful
 > > to have it for definition of both, "regular" and "digest".
 > > 
 > > Is this documented somewhere?
 > 
 > I don't think so.

I thought I had seen it "somewhere", but I can't find it now.  It
should be here:
https://docs.mailman3.org/projects/mailman/en/release-3.1/src/mailman/rest/docs/templates.html#templated-texts.

See https://gitlab.com/mailman/mailman/-/issues/1243.

Besides templates.html, this should be documented briefly in the forms
for changing the generic, regular, and digest templates, something as
simple as adding "if empty, falls back to generic:template" would do
for the regular and digest specific templates, and "shadowed by
regular:template and digest:template" for the generic template.

Note that that is in the developer's documentation for the REST
API. :-(  We really need to reorganize the docs to be more
discoverable for typical admins.

 > >I think, I need to create a wiki for mailman3.

 > We have a wiki at https://wiki.list.org/ for all versions of
 > Mailman. See the first paragraph at that page for info on obtaining
 > write access.

But note that this is *not* appropriate for the wiki, which is more
oriented to FAQs and news.  Wikis are fine for formal documentation,
but only if that's the ground truth.  For better or worse, we chose
not to do that.

-- 
GNU Mailman consultant (installation, migration, customization)
Sirius Open Source    https://www.siriusopensource.com/
Software systems consulting in Europe, North America, and Japan
_______________________________________________
Mailman-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Archived at: 
https://lists.mailman3.org/archives/list/[email protected]/message/EHO24VSWTCOSN5DWFDMHHAPY432722TM/

This message sent to [email protected]

Reply via email to