- ThurWiki
- Macros
85 macros. No marketplace.
What in Confluence is an app with its own price per user is part of the product here: charts from tables, Excel on the page, draw.io, Git, bexio, ticket systems, Zabbix, CRM. And the macros you already know, you will find under familiar names.
Which Confluence macro becomes what.
Tested against a real customer's content: 917 pages, some 2900 macro occurrences, 36 different macros. The most frequent ones are all covered. Anything ThurWiki does not know leaves a visible line with its name during the import.
| 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, expand, anchor | Table of contents, Expand, Anchor | |
| status | highlighted text | no macro of its own: the status becomes a coloured highlight in the text |
| drawio | draw.io diagram | the drawing stays editable, draw.io runs in our house |
| view-file, viewxls | Word document, Excel sheet | attachments on the page; Excel optionally as a real table |
| children, pagetree | Sub-pages | pagetree keeps the depth from the macro, otherwise three levels |
| gallery | Gallery | |
| profile, mention | Mention a user | users have to exist beforehand |
| recently-updated, contentbylabel, livesearch, pagetreesearch | Page list | four Confluence macros, one building block with a mode |
| contributors, userlister | Contributors, User list | contributors counted from the versions |
| excerpt, excerpt-include | Excerpt, Include excerpt | content taken from the source at display time |
| jira | Issue, Issue list (Jira) | through the Jira connector, with JQL |
| tasks-report-macro | Tasks of a user | covers the most frequent case |
| table-chart | Chart | chart from the table above it; choose the series once |
| table-filter | (a property of the table) | you switch on the search field and sorting in the TABLE tab |
| widget, iframe | A note | embedded third-party content leaves a note on the page |
All 21 groups.
fetches content Macros marked in blue fetch their content from a source. What comes from the wiki itself – sub-pages, page lists, contributors – is always current. What comes from other systems such as bexio, Jira or Git is held by the page as a snapshot; the "refresh" button brings the latest one and creates a new version for it.
Notices 6
- Info
- Note
- Warning
- Tip
- Error
- Panel
Structure 8
- Expand
- Section
- Column
- Table of contents
- Page break
- Excerpt
- Include excerpt
- Page list
Content 7
- Code block
- Task list
- draw.io diagram
- Gallery
- Chart
- Multimedia
- Voice note or meeting
Content from outside 5
- Table from CSV
- Table from JSON
- Word document
- Excel sheet
- Markdown file
References 3
- Anchor
- Sub-pages
- Content of another page
People 5
- Mention a user
- Tasks of a user
- Contributors
- Pages of a user
- User list
Groupware 3
- Insert a contact
- Appointment
- Insert appointments
Characters 2
- Emoticons
- Special characters
E-mail 1
- Insert an e-mail
Git 5
- Issue list (Git)
- Single issue (Git)
- File from the repository
- Latest changes (Git)
- Pull and merge requests
Nextcloud 2
- File from Nextcloud
- Folder from Nextcloud
Seafile 2
- File from Seafile
- Folder from Seafile
bexio 6
- Contact
- Invoice
- Quotation
- Invoice list
- Project
- Recorded hours
ERP 5
- Customer or supplier (ERP)
- Invoice (ERP)
- Invoice list (ERP)
- Order or quotation (ERP)
- Product (ERP)
Jira 3
- Issue
- Issue list
- Project
Ticket system 3
- Issue
- Issue list
- Project
WHMCS 4
- Customer
- Services of a customer
- Tickets
- Single ticket
Abacus 3
- Record
- List
- History
CRM 5
- Customer
- Person
- Opportunity
- Case
- Notes
Software builds 2
- Build status (Jenkins)
- Code quality (SonarQube)
Operations 5
- Host status (Zabbix)
- Open problems (Zabbix)
- Graph (Zabbix)
- VM or container (Proxmox)
- Cluster overview (Proxmox)
The three macros in the ticket system group serve Mantis, Redmine, Request Tracker, Zammad and YouTrack. Pull and merge requests come from GitHub, Bitbucket and GitLab; Gogs does not have them. The Zabbix graph is drawn by the wiki itself, so that it survives printing. "Image or video" does not appear in the list: it comes into being when you drag an image or video file into the text.
Three building blocks, and how to find them.
Chart
From the table above it. Bars, lines, pie, several series. Confluence: the chart macro with the table inside the macro, or table-chart as an app.
File from the repository
With a line range and highlighting, fetched from Git instead of copied; one click brings the latest state. Confluence: marketplace.
Issue list (Jira)
JQL, assignees, status, priority, from Jira Cloud and Data Center. Who sees the content is up to you, through the rights of the space. Confluence: the Jira macro, and only for readers who have a Jira account.
The chooser
The INSERT tab, the Macro button. On the left the groups with a count, on the right the macros as cards with name and description. The search at the top covers every group. Each card has a question mark leading to its help. Once inserted, a macro stays editable.
Questions about the macros
Which Confluence macros exist in ThurWiki?
The common ones: column, section, code, info, note, warning, tip, panel, toc, expand, drawio, view-file, children, pagetree, gallery, status, anchor, profile, recently-updated, contentbylabel, livesearch, contributors, userlister, excerpt, excerpt-include, jira. They are converted during the import. Anything missing leaves a visible line naming the macro.
Do I have to buy macros on top?
No. All 85 macros are part of the product, including the ones that would be a marketplace app in Confluence: charts from tables, Excel and Word on the page, draw.io, voice notes with transcripts, approvals, Git, bexio, ticket systems, Zabbix, CRM, calendars. There is no marketplace and no price per user and per app.
What does "fetches content" mean?
The macro does not show what somebody typed into it, but what stands in the source: another page, an attached file or a connected system. Anything drawn from the wiki itself – sub-pages, page lists, contributors – is always current. From other systems such as bexio, Jira or Git the macro fetches the content when it is inserted and holds it with that version of the page. The "refresh" button brings the latest state and creates a new version for it; an older version shows the state at that time.
Can I build macros of my own?
ThurWiki has no scripting language for your own macros. Tell us which source you need on your pages; we will discuss with you how it gets into the wiki.
85 wiki macros without a marketplace: notice boxes, columns, tables of contents, excerpts, page lists, code, tasks, draw.io, gallery, charts from tables, voice notes and meeting recordings with transcripts, tables from CSV, JSON and Excel, Word and Markdown on the page, people, calendars, e-mail, Git with pull requests, Nextcloud, Seafile, bexio, Jira, ticket systems such as Mantis, Redmine, Request Tracker, Zammad and YouTrack, WHMCS, Abacus, CRM, Jenkins, SonarQube, Zabbix and Proxmox. Including the mapping of the Confluence macros column, section, code, info, note, warning, tip, panel, toc, expand, drawio, view-file, children, pagetree, gallery, status, anchor, excerpt, recently-updated, contentbylabel, livesearch, contributors and jira.
Your macros, our mapping, one trial import.
We import twenty of your pages and show you what became of every macro.