Doc Helpers ✍️

This page demos several important pieces for the documentation and is meant to support anyone who wants to update or extend the documentation. This is not material for XLT.

The following chapters show important pieces how to use this Hugo template for writing the XLT documentation. Please refer always back to the source code and check how each component is written.

Info Boxes

Just a blockquote. You can still use them. They are kinda boring.


You can reference keyboard keys in text, using the kbd shortcode.


Java Code


import foo;

public class Foo

Bash Code

foo@picard $./


That's some text with a footnote.[^1]

[^1]: And that's the footnote.

That’s some text with a footnote.1

Go to Load Testing.

(Actually you can build links to wherever in the hierarchy without a shortcode, just like this.)

From here

About XLT is a link from here and not higher up.

You can build external links by using the link markdown with complete URLs, however it is recommended to just use html links opening in a new tab or window.


An image that gets its source from src and is linked to large if this is given. Paths are relative to static/images/. The .Inner part is the caption.

Another image that is not linked to anything. If it is too wide for the window, it will be scaled by CSS (.img-fluid, .td-content img {max-width: 100%}).

To just use CSS scaling like above for your large image, but think it looks nicer in the text at less than 100% width, you can just pass a max-width parameter to the shortcode that will be included in the image CSS.

Yet another image. Note how neatly you can navigate between the large versions of all images of this page.

Another image using the imageres shortcode, which will resize images to a smaller preview using hugo’s image processing. For this, the source image must be part of the page resources (pages are in a folder as, images in same folder). The .Inner part is the caption.

Colored Text

Should you need colored text, use ctext in green or any other html compatible color code. If none is given, this defaults to grey .

XTC Permissions

Several XTC actions require certain user roles to be performed, either in project or organization context. Use this shortcode to quickly add the necessary role:

{{% permission type="project" role="reader" action="chew gum" %}}

To chew gum, your account must have the role of a reader within the project.

There is no inner part required for this shortcode. The parameters “type” and “action” are optional, the default looks like this:

{{% permission role="reader" %}}

To use this feature, your account must have the role of a reader within the organization.


To-Do Marker

To remind us that something needs to be done, it introduces a marked TODO at the position of the shortcode {{< TODO / >}}. TODO markers right now assume to be in the beginning because they make a little room on the right side - “”.

Optionally you can pass the parameter comment and provide some more information such as {{< TODO comment="More information in the title" / >}}.

Marked Text

{{< TODO >}}To mark some text use this.{{< /TODO >}}
To mark some text use this.

Markdown in a To-Do

{{% TODO %}}To use **markdown** in the to-do, use this.{{% /TODO %}}

To use markdown in the to-do, use this.

  1. And that’s the footnote. ↩︎

Last modified January 13, 2022