2018.2

the data model of the template. When they have, the JSON values are passed
to the template and the personalization scripts of the template will have
access to the values through the record's data fields. (See the Designer help:
Adding Variable Data.)
Warning
The JSON format is not validated by the plugin; it is passed as is to the
server.
Note
Only the first record or JSON object is processed, since this task can
only generate HTML output for a single record.
l
Embed all resources: Check this option to download the resources and embed them in
the HTML file.
l
Do not alter HTML: Check this option to prevent that the Create Web Content task
modifies the HTML. It is recommended to use this option if the template's resources are all
hosted outside of the template (for instance, on a CMS repository).
Note
By default, the Create Web Content task inserts a <base> meta tag in the generated
HTML, specifying a default URL and target for all links on the web page. By
pointing to the Connect Server the job was sent to, the <base> tag enables the
HTTP server to retrieve the resources that were saved with the Designer template.
Since the <base> tag corrupts local anchors - links to another location in the same
web page -, the task also replaces the HREF attribute of local anchors with
JavaScript code. With this modification, local anchors will work; however, relative
URLs with hashtags still won't work.
Modifying the HTML this way isn't useful when all resources are either embedded in
the HTML file, or hosted outside of the template. So when the "Embed all
resources" or "Do not alter HTML" options (or both) are checked, the <base> tag
Page 521