Templates
New 7.11
Standardize how a category of Article begins. A Template copies its content, content type, tags, and Custom Metadata into every new Article created from it — so a runbook, a design document, or an onboarding guide always starts from the same shape instead of a blank page. A Template can also use a Document Profile, and then supplies the starter text for each of the profile's sections.
- ✅ Start new Articles from a consistent, pre-approved shape
- ✅ Pair a Template with a Document Profile: the profile sets the structure, the Template fills in the starter text
- ✅ Keep reusable macro placeholders in the Template body
- ✅ Resolve Resource and C4 node macros from context when available
- ✅ Trace every Article back to the Template it came from

Animated walkthrough: Add Article > From Template…, pick the Template with Use, give the Article its title, add a line, Save, and View. {{ Resource.Name }} from the Template reads empty here: a Resource. variable is filled in only when the Article is created from a Resource. For a name that follows the item the Article is read for, use the document macro {{ entity.name }}.
Understanding Templates
A Template is a starting point for new Articles — its content, content type, tags, and Custom Metadata are copied into every Article created from it. Unlike a Snippet, a Template's content isn't included by reference: it's copied once, at creation, and the new Article is then free to diverge from it.
Two Articles created from the same Template. Each copy is independent after creation, but both remember their Source Template.
| Concept | Behavior |
|---|---|
| Copied at creation | Content, content type, tags, and Custom Metadata — plus the Document Profile and the text of each Content Part, when the Template uses a profile |
| Independent afterward | Editing the Template does not change Articles already created from it |
| Source Template | Recorded on the new Article; visible in the reader and relationship views |
Profile-Based Templates
New 7.11
A Template can use a Document Profile, just like an Article. The three document types then share the work:
The Document Profile (blue) owns the structure, the Template (orange) owns the starter text for each Content Part, and the Article (green) is the instance a user writes.
| Owns | |
|---|---|
| Document Profile | The structure: Snippet Parts and Content Part slots |
| Template | Starter text for each Content Part, plus tags and Custom Metadata |
| Article | Its own text, written from that starting point |
- Editing the Template — choose a Document Profile in the Template editor, and the Template is shown in the same composite workspace as an Article: Snippet Parts locked, and one editor per Content Part for its starter text. The Template's reader shows the composed document.
- Creating an Article from it — the new Article starts profile-based: the Template's Document Profile is preselected, and the Main Body and every other Content Part start with the Template's text. Template variables found in any Content Part are listed to fill in, as for the Main Body.
- A Template without a profile — works as before: one body, copied into the new Article.
Seeded Example Template
On a new installation, Nodinite seeds the Standard Technical Base Template, which uses the seeded Standard Technical Article Document Profile. It supplies starter text for the profile's two Content Parts — Describe purpose and scope. for the Overview Main Body, and Describe implementation details and operational context. for Details — while the profile supplies the header, Next Step, Related Topics, footer, and copyright Snippet Parts.
Note
An upgraded installation keeps the seeded Template it already has: a single body with its own headings and Snippet include tokens, and no Document Profile.
New 7.12 The seeded Template is marked Shipped by Nodinite: it can't be edited or deleted, and every Nodinite upgrade updates it in place. Clone it to make your own version. See Shipped by Nodinite.
Macros in Template-Based Articles
Templates can contain the same macros as regular Articles. Macro placeholders are kept in the content and resolved when the Article is displayed.
| Macro group | Example | Resolution behavior |
|---|---|---|
| Date and time | {{ today }}, {{ now.utc }} |
Resolved at display time |
| Article | {{ article.title }}, {{ article.url }} |
Resolved from the current Article |
| Environment | {{ environmentname }} |
Resolved from the active environment |
| Resource / C4 node | {{ resource.name }}, {{ node.name }} |
Resolved when the Article is opened in the matching context |
A Template can also hold content tokens, including {ndx} inline icons placed with Insert Icon, the same icons as Component Types (requires a Mapify license). Like the rest of the content, they're copied into each new Article; see Inline Icons with .
The editor's Template Guidance card starts Templates are starting points and are not bound to Resources, Categories, Applications, Repository items, or C4 nodes. It then explains that a Template may use a Document Profile, whose sections become the starter text of every new Article, and that a Template without a profile can compose with reusable Snippets. Last, it separates template variables such as {{ CurrentYear }} and {{ CurrentDate }}, filled in once when the Article is created, from document macros such as {{ article.title }} and {{ entity.name }}, resolved every time the Article is rendered for the item it is read for. Macro help lists them all; see the Macros Reference.
Which template variables are filled in depends on where you create the Article:
{{ CurrentYear }}and{{ CurrentDate }}are always filled in once, when the Article is created from the Template.{{ Resource.Name }}and every otherResource.,Category.andApplication.variable is filled in only when the Article is created from that Resource, Category or Application. Created from the Articles list (Add Article › From Template…), there is no Resource, so the variable stays in the text as written, and the reader shows it as an unknown macro: empty.- For a name that should follow the item the Article is read for, use a document macro such as
{{ entity.name }}instead of{{ Resource.Name }}.

The Template Guidance card in the editor: template variables are filled in once, document macros every time the Article is rendered.
Create an Article From a Template
- Start creating a new Article
- Choose Create From Template
- Pick a Template from the list
- The Article's content, content type, tags, and Custom Metadata are copied in; for a profile-based Template, the Document Profile is preselected and each Content Part starts with the Template's text
- A banner in the editor reads Initialized from template (name), with a link to the Template. Give the Article its title and click Save
You can also start from a Template in one click: the Add Article dropdown's From Template…, the Create Article From Template row action on the Templates overview, and the Create Article from this Template button on a Template's editor and reader pages. See Ways to Create an Article for every entry point and the templateId deep link. When a link carries both templateId and profileId, a profile-based Template's own Document Profile wins.

Example of choosing a Template while creating a new Article.
Macro Resolution Context
Some macros need context from where the Article is opened:
- Opening the Article from a Resource provides
resource.*values - Opening the Article from a C4 diagram node provides
node.*values
If that context is missing, for example when the Article is read from the Articles list, those macros render empty; they resolve when the Article is viewed in a matching context. The editor and its preview always show them as typed. Macros are not template variables: a variable the editor can't resolve asks for its value with Apply Variables when you create the Article (see Template Variables and Macros).
Source Template Tracking
An Article created from a Template remembers it. The reader and relationship views show Based On Template, linking back to the Template it came from — even after the Article's own content has since changed completely.
Copy an Article as a Template
New 7.11
Your best Article is often the best starting point for the next one. Copy as Template turns an existing Article into a new Template, and leaves the Article itself untouched.
- Choose Copy as Template, either from the Article's row Action menu on the Articles overview, or from the Clone dropdown in the Article editor's header
- The Duplicate dialog suggests the title
(Template) ; change it if you like - Confirm — the new Template is created, and it opens in the browser

Example of Copy as Template in the Article editor's Clone dropdown.
| What happens | Behavior |
|---|---|
| Copied | Title (as entered in the dialog), content, content type, tags, Custom Metadata, and the Document Profile when the Article uses one |
| Not copied | Resource, Application, and Category links, because a Template has none of them |
| Profile-based Article | The Template keeps the Article's Document Profile: the Main Body becomes the Template's body, and every other Content Part keeps its text as starter text. The Snippet Parts still come from the profile, so they aren't copied into the Template |
| Plain Article | The Template gets the Article's single body, as is |
| Relationship | The Template's Clone Source points at the original Article, so the relationship views show where it came from. It has no Source Template |
| Original Article | Not modified. There's no in-place conversion: a document's kind never changes after it's created |
| Permission | Create Article (Repository_Article_Create), the same as Add and Clone |
Copy as Template is available for Articles only. To go the other way, create an Article from the Template as described above.
Web API
Copy as Template uses the existing duplicate endpoint of the Nodinite Web API with a new optional query parameter, targetDocumentType:
POST api/Articles/{id}/Duplicate?targetDocumentType=Template
Content-Type: application/json
{ "Name": "Incident Runbook (Template)" }
targetDocumentType |
Result |
|---|---|
| Omitted | A copy of the same kind, as before |
Template (or 2), with an Article as the source |
The copy is written as a Template, following the rules above |
| Any other value that changes the kind | 400 Bad Request, with an input error on TargetDocumentType |
The request body is unchanged, and the response is the created document with 201 Created.