Feature request - `{domain.logo}`
Tim & I discussed the other day adding the {domain.logo}
token. As always when this comes up we started with 'it would be very easy to do this minimal version' and by the end of the discussion the scope was un-manageable as unsponsored work.
However, I think the thing we CAN do is document it....
The easy way
{domain.logo}
refers to the image (if any) in the image_url field for the domain contact. That's it.
Probably we would need a version with <img>
tags & one without.
But then ... sizing & ^^ is too basic/ limited So next most complex is to use a setting. Once we start down this path we wind up having to develop a UI, handling sizing and it seems we might as well skip to....
Mailing Component tokens
In this version we would add a new component type to civicrm_mailing_component
and rows of this type would be available as tokens using {domain.{civicrm_mailing_component.name}}
. Placeholders ones for '{domain.logo}' and '{domain.header}' would be added. The existing UI could be used.
And still spiralling
- from there we got into trying to make it possible to nest the above, to use regions, to do the sort of thing the
entity_messages
token attempted to whereby we could store entity-related snippets (the idea was both to be able to insert a contribution specific block and to store entity-specific text to re-use - e.g to re-send an invoice with the original form-base message text)