feat(postcard): mail partials, built-in layouts and layout and partial overrides
- pact.HasMailPartials: plugins declare <plugin>::mail.partials.<name>,
loaded from views/mail/partials/<name>.htm; HasMailTemplates is unchanged
- bodies and layouts call {{ partial "name" "key" value ... }}; a call in a
Markdown body leaves a per-render random token swapped after goldmark, so
raw HTML stays disabled for bodies
- built-in partials button, panel, table and subcopy, built-in layouts
system and minimal next to the unchanged default, reachable by alias
after a plugin's own aliases
- NewDBSource also reads customized and database-only layouts and
customized partials; a layout's CSS goes before mail.css
Plan 35-01, task 3.
This commit is contained in:
@@ -1274,6 +1274,19 @@ type HasMailTemplates interface {
|
||||
MailLayouts() map[string]string
|
||||
}
|
||||
|
||||
// HasMailPartials is implemented by plugins that ship mail partials: reusable
|
||||
// blocks that mail template bodies and layouts call with
|
||||
// {{ partial "<name>" "key" value ... }}. MailPartialsFS contains the
|
||||
// views/mail assets; MailPartials lists dotted names of the form
|
||||
// <plugin>::mail.partials.<name>, each loaded from
|
||||
// views/mail/partials/<name>.htm. A plugin may only declare names in its own
|
||||
// namespace. The capability is independent of HasMailTemplates: a plugin may
|
||||
// implement either or both.
|
||||
type HasMailPartials interface {
|
||||
MailPartialsFS() fs.FS
|
||||
MailPartials() []string
|
||||
}
|
||||
|
||||
// OptionalMessage is a service an optional plugin may publish so other
|
||||
// plugins can integrate without importing that plugin's package.
|
||||
type OptionalMessage interface {
|
||||
|
||||
Reference in New Issue
Block a user