campaign
Advanced tools
Comparing version 1.5.0 to 1.6.0
@@ -0,1 +1,5 @@ | ||
# 1.6.0 `JSON-LD` | ||
- Campaign now forwards the `linkedData` property to the layout template | ||
# 1.5.0 Bug as a Service | ||
@@ -2,0 +6,0 @@ |
@@ -14,3 +14,3 @@ { | ||
}, | ||
"version": "1.5.0", | ||
"version": "1.6.0", | ||
"licenses": "MIT", | ||
@@ -17,0 +17,0 @@ "keywords": [ |
@@ -239,3 +239,3 @@ ![campaign.png][9] ![ga](https://ga-beacon.appspot.com/UA-35043128-6/campaign/readme?pixel) | ||
The `layout` has one fundamental requirement in order to be mildly functional, it should have a `{{{body}}}` in it, so that the actual email's content can be rendered. Luckily the default `layout` is good enough that **you shouldn't need to touch it**. If you're building a custom layout, `{{{body}}} should be whatever expression is needed to render the unescaped `<body>` HTML. | ||
The `layout` has one fundamental requirement in order to be mildly functional, it should have a `{{{body}}}` in it, so that the actual email's content can be rendered. Luckily the default `layout` is good enough that **you shouldn't need to touch it**. If you're building a custom layout, `{{{body}}}` should be whatever expression is needed to render the unescaped `<body>` HTML. | ||
@@ -253,3 +253,4 @@ Purposely, the layout template isn't passed the full model, but only a subset, containing: | ||
"social": "<options.social>", | ||
"styles": "<options.style>" | ||
"styles": "<options.style>", | ||
"linkedData": "<options.linkedData>" | ||
} | ||
@@ -256,0 +257,0 @@ ``` |
@@ -23,3 +23,4 @@ 'use strict'; | ||
social: model.social, | ||
styles: model.styles | ||
styles: model.styles, | ||
linkedData: model.linkedData | ||
}; | ||
@@ -26,0 +27,0 @@ if (options.provider.name === 'mandrill') { |
46685
444
422