# ThurWiki for newcomers – the 85 macros explained

> All 85 ThurWiki macros in 21 groups: notices, columns, voice notes, Excel, Git, bexio, Jira, tickets, Zabbix, Proxmox, CRM. With a Confluence list.

Quelle: https://thurwiki.ch/en/basics/macros.html  
Anbieter: ThurData GmbH, Siegershausen, Schweiz  
Sprache: Deutsch (Schweiz)

---

- [ThurWiki](https://thurwiki.ch/en/basics/index.html)

- Macros

# 85 macros. Some shape the page, others fetch.

A macro is a ready-made building block you put into the page. Some are presentation: a notice box, columns, a table of contents. Others fetch their own content: from the wiki, in which case they are always current, or from a connected system, in which case they are fetched rather than typed out and brought up to date with one click.

## Inserting instead of building.

The INSERT tab, the Macro button: the macro chooser opens. On the left stand the groups, on the right the macros as cards, each with a short description of what the macro does. At the top a search field covers every group, and beside each group stands how many hits it has. On each card a question mark leads to the matching help. Once inserted, a macro stays editable: one click, and its settings are in front of you.

- **With a search across every group.** Type "invoice" and you see the macros from bexio and WHMCS. Type "column" and you see Section and Column (the column area and the column itself).

- **With help.** Every one of the 85 macros has a help text of its own: what it is good for, what the fields mean, where the pitfalls lie.

- **With a refresh.** A macro that fetches content from a connected system has a button for it. The state is shown with its timestamp, and every refresh produces a new version in the history.

*Bild: The macro chooser: on the left the groups with a count, on the right the macros as cards with descriptions, search at the top.*

**The macro chooser.** Ordered by group, with a search field and a question mark.

## All 21 groups.

Besides the building blocks for presentation and content, every connected program has a group of its own: the accounts, the ticket system, the server monitoring, the file store. Marked in blue are the macros that fetch their own content: from the wiki, from an attached file or from a connected system.

fetches content from the wiki always current; from connected systems fetched rather than typed out, brought up to date with one click.

### Notices 6

Boxes in five colours, so that the reader sees from the colour what is at stake. Plus the panel, a box with a border, title and background of its own.

- Info

- Note

- Warning

- Tip

- Error

- Panel

### Structure 8

Columns (Section for the column area, Column for the column itself), collapsible sections (Expand), a table of contents built from the headings, a page break for printing, excerpts and page lists.

- Expand

- Section

- Column

- Table of contents

- Page break

- Excerpt

- Include excerpt

- Page list

### Content 7

Code with highlighting, checklists, draw.io drawings, galleries, charts from tables, video and audio. Plus the [voice note](https://thurwiki.ch/en/basics/features.html#sprachnotiz): an audio recording on the page, optionally with a transcript, that is, the text written out. A single image needs no macro: drag the file into the text and you are done.

- Code block

- Task list

- draw.io diagram

- Gallery

- Chart

- Multimedia

- Voice note or meeting

### Content from outside 5

Tables from a spreadsheet file (CSV) or from another program's data (JSON), attached Word and Excel files and Markdown, shown on the page instead of downloaded.

- Table from CSV

- Table from JSON

- Word document

- Excel sheet

- Markdown file

### References 3

Anchors to jump to, the list of sub-pages, and the content of another page, fetched at display time rather than copied.

- Anchor

- Sub-pages

- Content of another page

### People 5

Who is responsible, who has contributed, which tasks are still open for somebody: drawn from the wiki, not typed out.

- Mention a user

- Tasks of a user

- Contributors

- Pages of a user

- User list

### Groupware 3

Calendar and address book: a contact, an appointment or an extract from the calendar, over the CalDAV and CardDAV standards, from Kerio, Nextcloud or Zimbra for instance.

- Insert a contact

- Appointment

- Insert appointments

### Characters 2

Emoticons and special characters, with a search field, for arrows, units of measurement and everything missing from the keyboard.

- Emoticons

- Special characters

### E-mail 1

A message from a mailbox, with sender, date, subject and attachments, placed in the minutes in which it was discussed.

- Insert an e-mail

### Nextcloud 2

Nextcloud is a file store that many companies use like a drive on the internet. The wiki shows a text file from it, optionally only an extract, or lists what sits in a folder.

- File from Nextcloud

- Folder from Nextcloud

### Seafile 2

The same for Seafile, another file store: a text file from a library, optionally only an extract, or the contents of a folder.

- File from Seafile

- Folder from Seafile

### Git 5

From Gogs, GitHub, Bitbucket and GitLab, the stores for source code (repositories): issues, a single issue, a file with a line range, the latest changes and the pull requests. Those are proposed changes waiting to be reviewed; in GitLab they are called merge requests.

- Issue list (Git)

- Single issue (Git)

- File from the repository

- Latest changes (Git)

- Pull and merge requests

### Software builds 2

For companies that develop software: the result of the last run from Jenkins, the tool that builds and tests software automatically, and the code quality from SonarQube, which examines the source code for faults.

- Build status (Jenkins)

- Code quality (SonarQube)

### Operations 5

For IT operations. From Zabbix, the monitoring of servers and devices: the state of a host (a monitored device), the open problems and the history of a measurement as a chart. From Proxmox VE, the platform for virtual servers: a VM (a virtual machine) or a container, and the overview of the whole cluster.

- Host status (Zabbix)

- Open problems (Zabbix)

- Graph (Zabbix)

- VM or container (Proxmox)

- Cluster overview (Proxmox)

### bexio 6

Contact with master data and finances, invoice and quotation with their line items, invoice list by status, project with recorded hours.

- Contact (bexio)

- Invoice (bexio)

- Quotation (bexio)

- Invoice list (bexio)

- Project (bexio)

- Recorded hours (bexio)

### ERP 5

For companies with Odoo or Flectra instead of bexio: customer or supplier with address and latest invoices, a document with its line items, a customer's invoices (only the outstanding ones if you wish), order or quotation, an article with price and stock.

- Customer or supplier (ERP)

- Invoice (ERP)

- Invoice list (ERP)

- Order or quotation (ERP)

- Product (ERP)

### Jira 3

An issue as a card, an issue list from a Jira search (JQL), a project with its open issues. Cloud and Data Center.

- Issue (Jira)

- Issue list (Jira)

- Project (Jira)

### Ticket system 3

A ticket system records enquiries and faults as issues. From Mantis, Redmine, Request Tracker, Zammad or YouTrack: an issue with its status and assignee, a list of open or finished issues, a project with its most recently changed issues.

- Issue

- Issue list

- Project

### WHMCS 4

For IT providers: the customer, their services, their tickets and a single ticket with its history, fetched from the billing system.

- Customer (WHMCS)

- Services of a customer (WHMCS)

- Tickets (WHMCS)

- Single ticket (WHMCS)

### Abacus 3

A record, a list and the history: what a record looks like today and how it has changed since it was connected, from the wiki's archive.

- Record (Abacus)

- List (Abacus)

- History (Abacus)

### CRM 5

From SuiteCRM and vtiger: customer, person, opportunity, case and the notes belonging to them, on the page of the project they belong to.

- Customer (CRM)

- Person (CRM)

- Opportunity (CRM)

- Case (CRM)

- Notes (CRM)

## Four macros in use.

*Bild: The page*

**Chart.** It takes the figures from the table above it. Change the table and all three charts change with it.

*Bild: A wiki page with the macro*

**File from the repository.** The sample configuration from Git, directly on the page. If it has changed in the repository, one click brings the new state; the old version stays in the history.

*Bild: A wiki page with the issue list from Jira: key, title, status, assignee and priority, below that a single issue as a card with its description.*

**Issue list (Jira).** What is open right now, with assignee and status. Whoever reads the page need not open Jira.

*Bild: A page embedding a named excerpt of another page, with a note about its source.*

**Include excerpt.** The same paragraph on five pages, maintained on one. A copy would quietly go out of date; that is exactly what this macro prevents.

## For people coming from Confluence: which macro becomes what?

During the import, ThurWiki converts the common Confluence macros. Anything it does not know leaves a visible line with the macro's name and an entry in the import report. Nothing quietly disappears – that would be the worst thing an import can do.

| Confluence | ThurWiki | Note |
|---|---|---|
| column, section | Column, Section | column widths are carried over |
| code | Code block | with language and highlighting |
| info, note, warning, tip | Info, Note, Warning, Tip | one box each, in the matching colour |
| panel | Panel | title, border and background are kept |
| toc | Table of contents | levels from and to |
| expand | Expand |  |
| drawio | draw.io diagram | our own draw.io installation, the drawing stays editable |
| view-file, viewxls | Word document, Excel sheet | attachments are shown on the page |
| children, pagetree | Sub-pages | pagetree with depth 3 |
| gallery | Gallery |  |
| status | coloured highlighted text | no macro of its own; the status becomes a coloured highlight in the text |
| anchor | Anchor |  |
| profile, mention | Mention a user | users have to exist beforehand |
| recently-updated, contentbylabel, livesearch, pagetreesearch | Page list | four Confluence macros that list or search pages; in the wiki they all become the page list |
| contributors, userlister | Contributors, User list |  |
| excerpt, excerpt-include | Excerpt, Include excerpt |  |
| tasks-report-macro | Tasks of a user | covers the most frequent case: the tasks of one person |
| table-chart | Chart | chart from the table above it; the import places the macro, you choose the series once |
| widget, iframe | – (no macro) | embedded third-party content is not carried over; a visible note remains on the page |
| jira | Issue, Issue list (Jira) | through the Jira connector, with the same queries |

The basis: a count across a real customer's content, against which we tested the import: 917 Confluence pages with some 2900 macro occurrences. The macros most frequent there are all covered.

## Questions about the macros

**What is a macro in ThurWiki?**

A ready-made building block you put into a page: a notice box, a column layout, a table of contents, a chart, an invoice from bexio. Some are purely presentational, others fetch their own content: from the wiki, in which case they are always current, or from a connected system, in which case they are fetched rather than typed out and brought up to date with one click.

**How do I insert a macro?**

Through the INSERT tab and the Macro button. The macro chooser opens: on the left the groups, on the right the macros as cards with a short description, at the top a search across every group. On each card a question mark leads to its help. Once inserted, a macro stays editable: one click opens its settings.

**Where does the content of the bexio, Jira or Git macros come from?**

From the connected system, through an access the wiki administrator sets up once. The macro fetches the content when it is inserted and holds it with that version of the page. It fetches anything new at the press of a button ("refresh"); that produces a new version in the history. Access is read-only; the wiki writes nothing back.

**What happens to Confluence macros during the import?**

The common ones are converted: columns, code, sections, info, warning, note, tip, panel, table of contents, sub-pages, draw.io, attachment preview, gallery, anchors, mentions, recently updated, page lists; a status becomes a coloured highlight in the text. Unknown macros remain on the page as a visible note and appear in the import report.

**Can I build macros of my own?**

ThurWiki has no scripting language for your own macros, and needs no marketplace either. If a source is missing for you, talk to us; we will look at whether and on what terms we can build it in.

[**The 41 connectors** The connections through which the blue macros get their content, and how access is set up](https://thurwiki.ch/en/basics/connectors.html) [**All the features** Editor, tables, search, versions, approvals, images, mobile](https://thurwiki.ch/en/basics/features.html) [**Migrating from Confluence** Import in five steps with a preview, comparison, tips for the move](https://thurwiki.ch/en/basics/migration.html)

## Try the macros on your own content.

In the demo wiki you see the macros at work, the connections to bexio, Jira and Git included. We will set it up for you.

[Request demo access](https://thurwiki.ch/en/basics/../demo.html) [On to the connectors](https://thurwiki.ch/en/basics/connectors.html)