Writing guideMarkdown guide

Markdown guide

This Markdown guide helps keep contributions consistent across all Grafana Labs documentation. Refer to the guide and update it as needed when a subject matter expert (SME) answers a question about Markdown syntax, or a decision is made about how to apply Markdown.

Write in sentence case throughout all technical documentation, be it long-form text or microcopy within a UI:

  • This is sentence case
  • This is Headline Case


Similar to HTML headings (<h1>, <h2>, and <h3>), in Markdown, # symbols (or hash tags) create different heading levels:


  • # is a parent heading.
  • ## is a child heading.
  • ### is a child’s child heading.

For the title of the page, use one #. For each child heading, use two ## symbols.

Heading don’ts

  • Avoid stacked headings; do not follow a heading with another without any content between the two.
  • Avoid skipping heading levels. For example, after a single #, use ##, rather than ###.
  • Avoid having just one child-level heading:
    • Valid: #, ##, ##, ###, ###, ##, ##
    • Invalid: #, ##, ###, ##, ###, ##
  • Avoid using hyphens in headings.
  • With the exception of (Optional) , do not include parenthesized words such as (Important).

Bold and emphasis

  • To make text bold, surround the text with **two asterisks**. For example:

    Note: It is important to use GitHub-flavored Markdown emojis consistently.

  • To emphasize text, surround the text with _single underscores_̣. Do not use single asterisks (*), because they can be easily confused with two (for bold).

**Note:** The distributor only passes _valid_ data to the ingesters.

Displays as:

Note: The distributor only passes valid data to the ingesters.

For information about creating links between topics inside and outside of a Grafana Labs repository, refer to Links and cross references.

If you want to add a link to an external website, wrap the display text in square brackets, and the web URL in curly brackets.

[Link text to display](https://example.com)

Example: For more information about including emojis in GitHub-flavored Markdown, refer to the WebFX Emoji Cheat Sheet.

Block quotes

Include block quotes within text by using a right-angle bracket:

> This text is in block quotes.


Any important information about emojis can be separated into a blockquote.

Code blocks

Code blocks within Markdown can highlight syntax that is specific to a language. Use three back tics to create a code block. For example, ``` immediately followed by javascript produces the following highlights:

function testNum(a) {
  if (a > 0) {
    return 'positive';
  } else {
    return 'NOT positive';


Construct a table by separating the table headings by a | (pipe) character. Then, add a second line of dashes (-) separated by another | character. When constructing the table cells, separate each cell’s data with a |.


| Heading one   | Heading two   |
| ------------  | ------------  |
| Cell one data | Cell two data |

When rendered, the preceding table displays as follows:

Heading oneHeading two
Cell one dataCell two data

Numbered lists

Use repetitive list numbering, to avoid inconsistent list numbering:

1. First
1. Second
1. Third

The preceding list displays as:

  1. First
  2. Second
  3. Third

Unordered lists

Build a list of unordered items by using a hyphen (-):

- First item
- Another item
- The final list item

Note: Use unordered lists whenever the items have no particular sequence.

The preceding snippet displays as follows:

  • First item
  • Another item
  • The final list item


Do not use image shortcodes at this time. Instead, include images in a document using the following syntax:

![Alt text](link to image, starting with /static/img/docs/ if it is to an internal image "Title of image in sentence case")

Note: Alternative text (alt text) doesn’t appear when the user hovers their cursor over the image. The title text does.


  • ![Grafana logo](/link/to/grafanalogo/logo.png "Grafana logo")
  • ![Example](/static/img/docs/folder_name/alert_test_rule.png "Example title")

This follows the format ![alt text](URL).

Within Markdown, HTML is valid and to be used sparingly:

<img src="example.png"
     alt="Example image"
     style="float: left; margin-right: 5px;" />

In most cases, use Markdown syntax rather than HTML syntax. Only use HTML if you need to change the image in ways that Markdown does not support.

Description list

The Markdown parser that Hugo uses, Goldmark, has built-in support for description lists. You can use description lists for terms and their definitions, or core concepts. The syntax is as follows:

: description_text

You can add more markup in a description list. For example, you can format the definition terms as bold text.

Reasons you might want to write programs in Go include the following:

**Fast compile times**
: The Go compiler is fast!

: Go tooling is excellent.

The preceding description list displays as follows:

Fast compile times
The Go compiler is fast!
Go tooling is excellent.


You can include comments that do not display in published output:

[comment]: <> (Comment text to display)


Shortcodes are predefined templates that let you reuse snippets of technical documentation. To learn how to use shortcodes, refer to Shortcodes.