Skip to content

Rich text (WYSIWYG) editor in Nepenthes

Starting with version 8.0.0, Nepenthes features a quasi-WYSIWYG editor, powered by CKSource CKEditor5. The underlying format is GitHub-flavored CommonMark (GFM). All previous textile-based content will be migrated when upgrading to Nepenthes 8.0.

Please note: In some resources such as work packages or comments, the editor does not exhibit all functionality such as macros or image upload. In the work package split screen view (details view) you may have to use the three vertical dots to access additional features of the editor.

Basic formattingBasic formatting elements in the WYSIWYG editor
Image handlingHow to add images in the WYSIWYG editor.
Keyboard shortcutsWorking with keyboard shortcuts in the WYSIWYG editor.
MacrosAvailable macros in the WYSIWYG editor
Links to Nepenthes resourcesHow to link to resources like wikis, projects, meetings.
Embedding of work package attributes and project attributesHow to embed attributes and attribute help texts.

Basic formatting

The CKEditor5 build in Nepenthes supports basic text styles, such as bold and italic formatting, headings, strike-through, inline code, and quotes as well as inline image handling. Pasting content such as images or rich text is also supported, while unsupported styling will be stripped by the editor.

Line breaks

Instead of creating a new paragraph with Enter, you can also press SHIFT+Enter to create a line break without creating a new paragraph.

Create hyperlinks by pressing the tool-bar (optionally with some selected text), or by pressing CTRL+k to open a popup to enter the link here.

Widgets and Newlines

CKEditor uses widgets to display block elements such as images, tables, and other elements that are not inline. You can select most widgets by pressing on it - The only exception to that is the table widget, it has a little select knob at the top left to select the entire table.

When you have a widget selected, you can remove or cut it. You can create a newline below it by selecting the widget and pressing ENTER or ↓ (ARROW DOWN), or a newline above it by pressing SHIFT+enter or ↑ (ARROW UP). This is especially needed when the widget is the first or last element on the page to insert a line below or above it.

Code Blocks

As CKEditor5 currently does not provide support for code blocks, Nepenthes can display, but not edit code blocks within the CKEditor instance. A code block can be edited through a modal window within a CodeMirror editor instance. This has the advantage of providing syntax highlighting and code sensing (for supported languages).


The GFM extension of the CommonMark specs adds a definition for table syntax which the CKEditor of Nepenthes supports. This definition requires all tables to have a heading row. For tables created with CKEditor without heading rows, a HTML table is output instead. This matches the behavior of, e.g., GitHub.


CKEditor5 allows certain CommonMark-like autoformatting keyboard strokes:

  • Create bold or italic styles by typing **will become bold**, _will become italic_,
  • Create heading of different indentation with #, ##, ###, …
  • Create a bulleted list by starting the line with * or - and a space
  • Create a numbered list by starting the line with 1. or 1) and a space

Image handling

In supported resources of Nepenthes where attachments are allowed, you can add images to the page by either

  • using the toolbar button,
  • pasting an image from your clipboard,
  • or drag & drop an image onto the editor.

The image will be automatically uploaded and stored as an attachment. You can adjust the image size in the editor using your mouse.

Resize Image

Keyboard shortcuts

CKEditor has a wide variety of keyboard shortcuts you can use. You can find a list of documented shortcuts here:

On top of that, Nepenthes adds the following shortcut:

Shortcut (Windows / Linux)Shortcut (Mac)Action
CTRL + ENTERCMD + ENTERSave changes.
For inline-editable fields, save the field and close it.
For pages with a full WYSIWYG (meetings, wiki pages), submit the form.


Nepenthes has supported macros on textile formatted pages and continues to do so with the WYSIWYG editor. Note that macros are not expanded while editing the page, instead a placeholder is shown.

You can find the macros here in the text editor: Macros text editor

Table of contents

Where applicable, the table of contents (TOC) macro will output a listing of all headings on the current page.

Work package button

Configure a button or link to target the work package creation screen in the current project. You can preselect a work package type that should be selected, making it easy to guide the users to the work package creation form.

Include wiki page

Include the content of a given wiki page in the current, or another visible project.

Embed work package table and Gantt chart

This is the most flexible macro that provides extensive functionality regarding the inclusion of dynamic work package tables with all the potential of the regular work package table.

By adding an embedded work package table through the toolbar, you can configure the table view (such as columns, grouping, filters, and further properties) in a popup window.

The rendered page will then fetch the work package table results dynamically, respecting the visibility for each user.

Use it to embed views in other pages, create reporting of multiple results, or to embed a Gantt chart view.

As with the textile formatting syntax, you can link to other resources within Nepenthes using the same shortcuts as before. Create links to a:

  • wiki page: [[Wiki page]]
  • wiki page with separate link name: [[Wiki page|The text of the link]]
  • wiki page in the Sandbox project: [[Sandbox:Wiki page]]
  • work package with ID12: #12
  • work package with ID 12 with subject and type: ##12
  • work package with ID 12 with subject, type, status, and dates: ###12
  • version by ID or name: version#3, version:"Release 1.0.0"
  • project by ID/name: project#12 , project:"My project name"
  • attachment by filename:
  • meeting by ID/name: meeting#12 , meeting:"My meeting name"
  • document by ID/name: document#12 , document:"My document name"
  • user by id or login: user#4 , user:"johndoe"
  • a forum message by ID: message#1218
  • repository revision 43: r43
  • commit by hash: commit:f30e13e4
  • To a source file in the repository: source:"some/file"

To avoid processing these items, preceding them with a bang ! character such as !#12 will prevent linking to a work package with ID 12.

Please note: All these macros need to be written as a new word (i.e., with at least one space before it or at the beginning of a paragraph/sentence. Macros contained within a word such as somethingmeeting#4 will not be parsed.

Autocompletion for work packages and users

For work packages and users, typing # or @ will open an autocompleter for visible work packages and users, respectively.

Embedding of work package attributes and project attributes

You can embed specific attributes of work packages or projects using a certain syntax. Examples:

  • Linking to the subject of work package with id #1234: workPackageValue:1234:subject (this also works for other attributes, too. See table below.)
  • Linking to the current project's status: projectValue:status
  • Linking to the subject of work package with subject "Project start": workPackageValue:"Project start":subject

Please note: Referencing a work package by subject results in only looking for work packages with that given subject in the current project (if any). If you need to cross-reference work packages, use their ID to pinpoint the work package you want to reference.

Embedding attribute help texts

You can also embed attribute values and their help texts by using workPackageLabel instead of: workPackageLabel:1234:status which would output the translated label for "Status" and (if exists), the corresponding help text for it.

Please note: These macros will only be expanded in the frontend. For each individual user, the correct permissions will be checked and the macro will result in an error if the user is not allowed to view the respective resource.


The following lists show the supported attributes for work packages and projects.

Please note: If you are using a language different than English, a translation of the commands can only be used in the text editor if the language of all the users of an instance is set to the same language (for example German). In this case, only the attribute to which the command refers is translated, e.g. (workPackageValue:1234:"translated attribute"). We recommend against using translated attributes, as they might break in future versions due to fixes or changes to texts.

Available attributes for work packages

The following list contains all supported attribute names for the workPackageValue and workPackageLabel macros, where 1234 stands for the work package ID.

AttributeUsage example
Custom FieldsworkPackageValue:1234:"Name of the work package custom field"
Creation dateworkPackageValue:1234:createdAt
Estimated timeworkPackageValue:1234:estimatedTime
Finish dateworkPackageValue:1234:dueDate
Parent work packageworkPackageValue:1234:parent
Remaining hoursworkPackageValue:1234:remainingTime (sic!)
Responsible userworkPackageValue:1234:responsible
Spent timeworkPackageValue:1234:spentTime
Start dateworkPackageValue:1234:startDate
Subject / TitleworkPackageValue:1234:subject
Work package typeworkPackageValue:1234:type
Date of last updateworkPackageValue:1234:updatedAt

Available attributes for projects

The following list contains all supported attribute names for the projectValue and projectLabel macros. The examples all show references to the current project the document is rendered in. They can also reference another project with projectValue:"Identifier of the project":attribute.

AttributeUsage example
Custom FieldsprojectValue:"Name of the project custom field"
Project active? (boolean)projectValue:active
Identifier of the projectprojectValue:identifier
Name of the projectprojectValue:name
Status descriptionprojectValue:statusExplanation
Parent projectprojectValue:parent
Project public? (boolean)projectValue:public