notifyrender

type Branding struct {
	// Name is the portal brand/title, e.g. "ACME Data Platform".
	Name string
	// BaseURL is the portal's public base URL used for deep links.
	BaseURL string
	// ImplementorName and ImplementorURL render in the footer when set.
	ImplementorName string
	ImplementorURL  string
	// TermsURL and PrivacyURL render as small legal links in the footer when
	// set. When the portal runs on a different domain than the mail From
	// address, they give recipients and content filters body links that
	// associate with the sending identity.
	TermsURL   string
	PrivacyURL string
	// AboutText and SupportContact render as a help/about footer block on
	// all outgoing mail when set (#1023). AboutText is a sentence or two
	// describing the platform; SupportContact is an email address or http(s)
	// URL for help. Implementor-owned YAML config (portal.about_text,
	// portal.support_contact), like the rest of the branding: in fully
	// managed deployments these are not admin-editable.
	AboutText      string
	SupportContact string
	// ReplyTo, when set, is stamped on every rendered Email so the sender
	// applies it as the Reply-To header and recipient replies reach a
	// monitored mailbox (#1023). From portal.reply_to.
	ReplyTo string
	// LogoPNG is the raster logo from portal.logo_email, resolved once at
	// startup. When non-empty it is attached to every message as an inline
	// (cid:) part and rendered above the wordmark; recipients never fetch it
	// remotely, so it survives the image blocking most clients apply by
	// default. Empty renders the wordmark alone.
	LogoPNG []byte
}

type Email struct {
	To      string
	Subject string
	HTML    string
	Text    string
	// LogoPNG is the inline logo the sender must attach under LogoContentID
	// when non-empty. The HTML references it but cannot carry the bytes.
	LogoPNG []byte
	// UnsubURL is the recipient's no-login unsubscribe link when the message
	// carries the footer opt-out (notifications only; transactional sends
	// leave it empty). The sender emits the RFC 8058 List-Unsubscribe headers
	// from it, so header presence tracks the footer link exactly.
	UnsubURL string
	// ReplyTo is the Reply-To address the sender must apply when non-empty
	// (#1023). Stamped from Branding.ReplyTo on every rendered message.
	ReplyTo string
}

type Renderer struct {
	// contains filtered or unexported fields
}