Formatting of posts
Sjaak Velthoven avatar
Written by Sjaak Velthoven
Updated over a week ago

The same formatting rules apply for the different posts around Catenda Hub.

Posts can include issue descriptions, comments approval descriptions and approval comments.
Variations can apply with the different access to who can edit the post.

Catenda uses markdown to format text.

This means that certain characters before and after sentences will affect the styling of the text.

Note: Many of the methods require a blank newline before it

The following topics will be described in this articled in this article:

Styling text

The following methods allow you to style your text:

Bold, italics, strikethrough

**This will be bold** 
__This will also be bold__
*This will be italics*
_This will also be italics_
**This will be bold _combined with italics_**
~~This text will be stiked through~~

This will be bold
This will also be bold
This will be italics
This will also be italics
This will be bold combined with italics
This text will be stiked through


## in front of some text will make a header


Links in descriptions will be green and underlined.

Their text can be different than the url that the link points to.

Urls will be automatically turned into clickable links

will become


[Catenda Hub](

will become:

Breaking up text and adding structure

The following methods let you enhance your text by breaking it up and adding structure:


Images in descriptions can have a link attached to them.

To embed images you can use this syntax


to get this image with the word text behind it.



Unordered lists

Use a - followed by a space

- First element 
- Second element
- to make a sublist just enter 4 spaces at the start of the line

this will turn into this:

  • First element

  • Second element

    • to make a sublist just enter 4 spaces at the start of the line

Ordered lists

Use a number followed by a period. What the number in front is, does not matter, just that it’s a number followed by a .

1. First item 
2. Second item
1. ordered sublist item.
2. to create a sublist one have to insert 4 spaces in front.
1. What the number is does not matter.

That will turn into this:

  1. First item

  2. Second item

    1. ordered sublist item.

    2. to create a sublist one have to insert 4 spaces in front.

  3. The value of the number does not matter.


Three dashes --- or more on their own line will create a divider:


These can be checked in the description by anyone with write access to the issue board.

- [ ] first item 
- [x] second item
- [ ] sublist item

Will turn into this:

Click here to watch a quick video on how checklists can be used in the project.

Checklists in comments cannot be clicked on to be checked as only the comment author is allowed to edit their comment.
If you write - [ ] or - [x] the box will still apear unchecked and checked when the comment is submitted or saved after editing.

Checkboxes in comments

In comments can only be checked by formatting and can only be changed by the commentor as they are the only one that can edit the comment.


Text in descriptions can be ordered in tables.

|            | Windows            ||             | 
| | Type 1 | Type 2 | Sum total |
|----------- | -------- | -------- | ----------- |
| **Price** | 500,- | 400,- | |
| **Amount** | 10 | 4 | |
| **Sum** | 5 000,- | 1 600,- | **6 600,-** |

will result in this


Type 1

Type 2

Sum total








5 000,-

1 600,-

6 600,-

Code blocks

You can insert single lines of code like this:
Two ` surrounding text will look like this:

Three backticks ``` above and below a bit of text will look like this:

It is not possible to add tables in code blocks

Markdown dialect

If you would like to know more about how text is formatted in comments and descriptions we use the markdown dialect "flexmark" to format this text.
Find out more about flexmark on their github page.

@ Mentioned members and teams

You can mention a user by typing @ and writing the account name of the user.

By clicking on a mentioned user or team you will be taken to the member page of that user or team page of that team.

Users and teams mentioned in the description of an issue will automatically follow the issue and thereby get notifications about future changes in the issue. This is a great way to ensure that more than just the assignee and requestee get notifications about future changes an issue.

# Tagged issues

You can tag issues by typing # and writing the number of the issue

After pressing enter tagged issues will then look like #[123] in the edited text. You can also manually write it like this.

After posting the text the link will dynamically show the color, status, title and issue number of the issue as well as contain a clickable link to this issue.

When you tag an issue that issue will be added to related issues in the right side panel.

The issue that was tagged will also have the issue where it was tagged in its list of related issues.

Issues can manually be removed from related issues.

Did this answer your question?