{{value-unescaped:foo}}

The {{value-unescaped:foo}} substitution parameter evaluates to the value of the header referenced by its rvalue.

However, unlike the {{value:foo}} parameter, the {{value-unescaped:foo}} parameter does not perform any HTML escaping.

For example, this node has a Foo header defined like this:

Foo: <i>Foo Header Value</i>

If we used the {{value:foo}} parameter on this page, it will be replaced with the HTML escaped value of the header when the page is rendered.

This is the HTML escaped value of the Foo header: <i>Foo Header Value</i>

However, if we use the {{value-unescaped:foo}} parameter instead, the HTML tags in the value will be passed directly through, causing the text to display in italic:

This is the unescaped value of the Foo header: Foo Header Value

HTML Escaping

When the HTML pages are rendered, the value of the {{value-unescaped:foo}} parameter will not be HTML escaped.

There is also another variant of this parameter, {{value:foo}}, which works identically, except that the values are HTML escaped.

Generally, you probably want HTML escaping most of the time, unless you have a compelling reason to intentionally bypass it.

Naming Convention

By convention, headers are set using Mixed-Case-With-Dashes. However, when they are referenced in substitution parameters, they are referenced in lowercase.

For example, a node might set a header and reference the same header directly like this:

Title: Some Example Node
Foo-Bar-Baz-Quux: Some Value

Here is the value of Foo-Bar-Baz-Quux: {{value:foo-bar-baz-quux}}

The example above would render in the generated page as:

Here is the value of Foo-Bar-Baz-Quux: Some Value

Tags: parameters