Macros Reference
New 7.11
Every macro and content token available in Nodinite Articles, in one place — what each one resolves to, and when it's available.
- ✅ Look up any macro by category instead of hunting through the editor
- ✅ Know exactly when a macro is available and when it isn't
- ✅ Understand which macros require Resource or C4 node context
- ✅ Use the same macros inside a Snippet as inside an Article
- ✅ Reference Snippets, images, files, Articles, and inline icons by name with content tokens
How Macros Resolve
A macro is a {{ name }} placeholder that resolves every time the document is displayed. This page lists every supported macro and where it resolves.
Core Facts
- Naming — macro names are case-insensitive
- Unknown macro — left as written, unresolved
- Full list — also available from the editor's Macro Help dialog
- Also resolve inside — Snippets, so a shared header or footer can show the current Article's own title, date, and so on
Example of the editor's Macro Help dialog.
Date and Time Macros
| Macro | Resolves to | Available when |
|---|---|---|
year |
The current year | Always |
today |
The current date | Always |
now |
The current date and time | Always |
year.utc, today.utc, now.utc |
The UTC equivalent of the macro above | Always |
Article Macros
| Macro | Resolves to | Available when |
|---|---|---|
article.title |
The Article's title | Always |
article.description |
The Article's description | Always |
article.id |
The Article's id | Always |
article.url |
The Article's URL | Always |
article.tags |
The Article's tags | Always |
article.created, article.created.utc |
When the Article was created | Always |
article.updated, article.updated.utc |
When the Article was last updated | Always |
Environment Macros
| Macro | Resolves to | Available when |
|---|---|---|
customername |
The value of the CustomerName system parameter | Always |
environmentname |
The current environment's name | Always |
product.version |
The running Nodinite version | Always |
currentuser.name |
The signed-in user's name | Always |
Resource Macros
| Macro | Resolves to | Available when |
|---|---|---|
resource.name, resource.type, resource.environment, resource.category, resource.application, resource.description |
The Resource's own field values | Shown for a Monitoring Resource |
resource.created, resource.created.utc, resource.updated, resource.updated.utc |
When the Resource was created or last updated | Shown for a Monitoring Resource |
resource.agentname, resource.logtext, resource.state |
The Resource's monitoring agent, latest log text, and current state | Shown for a Monitoring Resource |
C4 Diagram Node Macros
| Macro | Resolves to | Available when |
|---|---|---|
node.name, node.type, node.technology |
The bound node's own field values | Shown for a C4 diagram node |
node.componenttype |
The node's Component Type name | Shown for a C4 diagram node |
node.icon |
The Component Type's icon — Font Awesome, Azure, custom upload, or Mermaid | Shown for a C4 diagram node |
Warning
node.componenttypeandnode.icononly resolve on a C4 diagram node. They are not available on Systems, Integrations, or any other entity.
Content Tokens
A content token is different from a macro: instead of resolving a value, it references other Nodinite content by name, so a document stays portable between environments. You rarely type one by hand: each editable section has a toolbar that opens a picker and inserts the token for you.
The toolbar above every editable section. The picker buttons on the left insert content tokens; the button on the right opens Macro Help.
| Button | Inserts |
|---|---|
| Image | An {ndi} image from the Image Library |
| File | An {ndf} link to a file in the File Library |
| Article | An {nda} link to another Article |
| Snippet | An {nds} Snippet include |
| Icon | An {ndx} inline icon (requires the Mapify feature pack, see below) |
| Macro Help | Opens the Macro Help dialog, which lists every macro and content token |
Each token can also be typed or pasted directly into the Markdown:
| Token | References | Example |
|---|---|---|
{nds}/<slug> |
Includes the Snippet with that slug at this position | {nds}/std-header |
{ndi}/<name-or-id> |
The address of an image in the Image Library; use it as a Markdown image. A reference-style image takes an optional size: xxs, xs, s, m, l, xl, or xxl |
, or the reference style the image button writes: ![Logo][ndi-24][m] with [ndi-24]: {ndi}/company-logo, where 24 is the image id |
{ndf}/<name-or-id> |
The address of a file in the File Library; use it as a Markdown link | [Specification]({ndf}/spec-v2) |
{nda}/<slug-or-id> |
The address of another Article; use it as a Markdown link | [Overview]({nda}/erp-overview) |
{ndx}/<source>/<reference>[size] |
An inline icon from the same sources as Component Type icons — see below | {ndx}/fa/far/fa-cloud |
Inline Icons with
New 7.11
Put the same icons you use for Component Types straight into the text of an Article, Snippet, or Template: a cloud icon next to an Azure service, a brand icon next to a partner, or your own uploaded icon in a runbook step.
Important
The
{ndx}token requires a product key with the Mapify feature pack, the same feature pack that includes Component Type icon support. See License Options and Feature Matrix.
| Source | Reference | Example |
|---|---|---|
fa |
Font Awesome, as <style>/<name> |
{ndx}/fa/far/fa-cloud, {ndx}/fa/fab/fa-github |
azure |
An Azure service icon, as <category>/<file> |
{ndx}/azure/databases/10121-icon-service-Azure-Cosmos-DB.svg |
mermaid |
The Mermaid logo, as <category>/<file> (the only Mermaid icon shipped) |
{ndx}/mermaid/mermaid/mermaid.live.logo.svg |
custom |
An uploaded custom icon, by id | {ndx}/custom/12 |
Azure category folders can contain spaces and other special characters, which are URL-encoded in the token, for example {ndx}/azure/ai%20%2B%20machine%20learning/00028-icon-service-Batch-AI.svg. The icon picker writes the encoding for you.
Add an optional size in square brackets directly after the reference. The size names match the image size modifiers, but because icons sit inline with the text, they map to an icon scale rather than the image pixel widths:
| Size | Image icon | Font Awesome class |
|---|---|---|
| (none) | 20 px, the Component Type size | (none) |
xxs |
12 px | fa-2xs |
xs |
16 px | fa-xs |
s |
24 px | fa-sm |
m |
32 px | fa-lg |
l |
48 px | fa-xl |
xl |
64 px | fa-2xl |
xxl |
96 px | fa-3x |
Messages are archived in {ndx}/fa/far/fa-cloud Azure Blob Storage.
Source code lives in {ndx}/fa/fab/fa-github[l] GitHub.
Owned by the {ndx}/custom/12[m] Finance integration team.
Examples of inline icons: a Font Awesome icon at the default size, a brand icon at size l, and a custom uploaded icon at size m.
Note
Sizes are names only. A numeric suffix such as
[64]isn't recognized; like any unknown size name, it stays in the text as written, after the icon.