Your order ships free.
{{/if}} ``` | Helper | Test | | ------ | ------------------------ | | `eq` | equal | | `ne` | not equal | | `gt` | greater than | | `gte` | greater than or equal to | | `lt` | less than | | `lte` | less than or equal to | **`eq` and `ne` are strict**: no type coercion, so `(eq 1 "1")` is `false`. Watch for this with form posts, which often deliver numbers as strings. **The other four order numbers as numbers**, including numeric strings: `(gt "10" "9")` is `true`, because a form field carrying `"10"` still means ten. Two non-numeric strings compare alphabetically, which is what makes ISO dates work: ```handlebars {{#if (lt data.due_date "2026-01-01")}}Overdue{{/if}} ``` Values that can't be ordered (a missing field, a number against a word) make **all four false**. So on absent data, neither half of a `gt` / `lte` pair renders, rather than both guessing. Use `{{#if data.total}}` first if you need to handle "no value" explicitly. To branch across more than two values, [`switch` / `case` / `default`](#switch-case-default) reads better than a chain of `{{else if (eq …)}}`. ## `and` / `or` / `not` Combine conditions. All three are truthiness tests that match `{{#if}}` exactly, so `0`, `""`, and an empty list all count as absent. `and` and `or` take any number of arguments. ```handlebars {{#if (and (not data.paid) (gt data.amount_due 0))}}Payment overdue.
{{/if}} {{#if (or data.phone data.email)}}We'll be in touch.
{{/if}} ``` `not` is not the same as `{{#unless}}`: `unless` is a block, so it can't nest inside a condition. Reach for `not` when a negation needs to sit **inside** an `and` / `or`, as above. ## `formatDate` `{{formatDate value "pattern"}}` → a date, formatted. JSON carries dates as ISO strings, and no email should show a human `2026-10-15T10:30:00Z`. ```handlebars {{formatDate data.appointment}} → 15 October 2026 {{formatDate data.appointment "dd/MM/yyyy HH:mm"}} → 15/10/2026 10:30 {{formatDate data.appointment "EEEE, d MMM"}} → Thursday, 15 Oct ``` The pattern is optional and defaults to `d MMMM yyyy`. ### Tokens | Token | Output | | Token | Output | | ------ | --------------- | --- | ----- | -------------------- | | `yyyy` | 2026 | | `HH` | 09 (24-hour, padded) | | `yy` | 26 | | `H` | 9 (24-hour) | | `MMMM` | October | | `hh` | 09 (12-hour, padded) | | `MMM` | Oct | | `h` | 9 (12-hour) | | `MM` | 10 | | `mm` | 05 | | `M` | 10 (no padding) | | `m` | 5 (no padding) | | `EEEE` | Thursday | | `ss` | 45 | | `EEE` | Thu | | `s` | 45 (no padding) | | `dd` | 15 | | `a` | AM / PM | | `d` | 15 (no padding) | | | | Any other character passes through, so `d/M/yyyy` and `d.M.yyyy` both work. ### Quote your literal words Letters in the pattern are tokens, so a bare word gets eaten: the `a` in `at` becomes `AM`. Wrap literal text in single quotes: ```handlebars {{formatDate data.appointment "d MMMM 'at' HH:mm"}} → 15 October at 10:30 ``` Write `''` for a literal apostrophe. ### Time zone **Dates are formatted in UTC unless you say otherwise.** This is deliberate: the editor preview runs in your browser and the real send runs on the server, so a zone-dependent default would make the preview lie. Pass `tz` (any [IANA zone](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones)) to shift, and daylight saving is handled for you: ```handlebars {{formatDate data.appointment "HH:mm" tz="Europe/Berlin"}} → 12:30 ``` ### Language Pass `locale` (any BCP 47 tag) to translate month names, weekday names, and AM/PM. Numbers stay as digits, and a locale never rewrites `dd/MM/yyyy`. ```handlebars {{formatDate data.appointment "EEEE, d. MMMM yyyy" locale="de-DE"}} → Donnerstag, 15. Oktober 2026 ``` ### When the value isn't a date A missing or empty value renders nothing. A value that can't be parsed renders **as-is**, rather than disappearing. An appointment email that silently drops its date is worse than one showing a value you can see is wrong in the preview. An unusable `tz` or `locale` falls back to the default instead of failing the render. Accepted inputs are an ISO 8601 string (recommended), a `Date`, or epoch **milliseconds**. A seconds-based timestamp (as some webhooks send) will render as 1970, so multiply by 1000 first. ## `icon` `{{icon "github"}}` → renders an icon as an ``, no stylesheet, nothing Outlook's Word renderer strips.
Two forms:
```handlebars
{{! block form: hand-authored; the body is normal Handlebars }}
{{#codeblock lang="js" theme="postcraft-dark"}}
const key = "{{{apiKey}}}";
{{/codeblock}}
{{! src form: what the visual Code block emits; base64url-encoded source }}
{{codeblock src="Y29uc3QgeCA9IDE7" lang="js" theme="postcraft-dark"}}
```
Both forms interpolate the source, so a snippet can carry runtime data: `const ref = "{{bookingRef}}";` renders the recipient's own reference. To show the braces themselves, which is what a snippet _about_ a template language needs, escape them the Handlebars way:
```handlebars
{{#codeblock lang="handlebars"}}
Hi \{{ firstName }}
{{/codeblock}}
```
The difference between the forms is only where the source lives. In the block form the body sits in the template, so an unbalanced `{{` in it breaks the surrounding parse. The `src` form keeps the source out of that parse, which is why the visual Code block uses it: a pasted snippet that is not valid Handlebars renders verbatim instead of taking the template down.
**Options:**
| Option | Meaning |
| -------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| `lang` | `js`, `ts`, `tsx`, `json`, `bash`, `html`, `css`, `python`, `go`, `php`, `ruby`, `java`, `sql`, `yaml`, `handlebars`, or `plain` (default: `plain`) |
| `theme` | `postcraft-light`, `postcraft-dark` (default), `github-light`, `github-dark`, `nord`, `dracula`, `one-dark-pro`, `catppuccin-mocha` |
| `bg` | Panel background override, e.g. `bg="#0b1021"`; token colors stay the theme's own |
| `radius` | Corner radius in px, `0`–`64` (default: `6`); `radius=0` squares the panel |
| `src` | base64url-encoded source; used instead of a block body |
The picked theme is absolute: a panel keeps its own background and ink on light and dark rows alike. Unknown `lang` or `theme` values fall back to `plain` / the default theme rather than failing the render, and source longer than 16 KB is truncated.
## `nl2br`
`{{nl2br value}}` → HTML-escapes the input and converts newlines (`\n`, `\r\n`, `\r`) to `
` tags.
```handlebars
{{nl2br comment}}
```
The input is escaped _first_, so only the literal `
` Postcraft inserts is trusted output. Safe to use with user-submitted text.
## `pluralize`
`{{pluralize count "noun"}}` → emits `count + " " + noun` (with a default `+s` plural).
```handlebars
{{pluralize 1 "item"}}
→ 1 item
{{pluralize 5 "item"}}
→ 5 items
{{pluralize 2 "child" "children"}}
→ 2 children
```
Optional third positional argument overrides the default plural for irregular nouns.
## `sanitizeUrl`
`{{sanitizeUrl url}}` → returns the URL if it passes the safe-URL allowlist (`http`, `https`, `mailto`, `tel`, relative, anchor), otherwise returns `#`.
```handlebars
…
```
The visual-mode button renderer wraps variable-bound `href` values in this helper automatically, so a context value like `javascript:alert(1)` cannot produce a clickable XSS link. Use it explicitly in code-mode templates when you embed user-controlled URLs.
## `stringify`
`{{stringify value}}` → JSON-serializes the value. Optional `indent=N` pretty-prints with N-space indentation.
```handlebars
{{stringify data}}
→ {"a":1,"b":2}
{{stringify data indent=2}}
→ { "a": 1, "b": 2 }
```
Useful for debug previews and for embedding structured data into `