# Text Widget

Learn how to use Markdown in the Text widget whenever you need to create explanations, instructions, or contextual information in your dashboards.

### How to apply basic formatting?

{% stepper %}
{% step %}
**Italics**

Use single asterisks or single underscores to format text in *italics*. Example:

\*text\* or \_text\_

![](/files/S0vAyrBscdCee896ndrY)
{% endstep %}

{% step %}
**Bold**

Use double asterisks or double underscores to make text **bold**. Example:

\*\*text\*\* or \_\_text\_\_

![](/files/EGLfyyFvrN9tRFLAPssf)
{% endstep %}

{% step %}
**Bold + Italics**

Use three asterisks or three underscores to combine ***bold and italics***. Example:

\*\*\*text\*\*\* or \_\_\_text\_\_\_

![](/files/BF2oV240lkUqKuwqjkN9)
{% endstep %}

{% step %}
**Strikethrough**

Use double tildes (\~\~) to strike through text. Example:

\~\~text\~\~

![](/files/8m1tuptKqVZR2rYfU3lO)
{% endstep %}
{% endstepper %}

***

### How to create titles and subtitles?

You can use six levels by adding # at the beginning of a line. The more hashtags you use, the lower the heading level.

\# Heading 1

\## Heading 2

\### Heading 3

\#### Heading 4

\##### Heading 5

\###### Heading 6

![](/files/kU02e2GYCbaIbbGxrO5e)

***

### How to create lists?

{% stepper %}
{% step %}
**Bullet lists (unordered)**

Use \*, - or + followed by a space. Example:

\- Item 1

\+ Item 2

\* Item 3

![](/files/ciSVORcBDzhz6D3bqMio)
{% endstep %}

{% step %}
**Task lists (checklists)**

Use - \[ ] or - \[x]. Example:

\- \[ ] Pending task

\- \[x] Completed task

![](/files/z732p5MtJ1AYFS0F8QOk)
{% endstep %}

{% step %}
**Nested lists**

Use four spaces or a tab to nest lists. Examples:

\* First level

\* Second level

\* Third level

![](/files/bLIHj2g94h1dTg3lDXc1)
{% endstep %}
{% endstepper %}

### How to add quotes?

Use > at the beginning of the line. Example:

\> Simple quote

\>> Quote inside another

![](/files/y4MIRAlV9FyhxCMmz5hp)

### How to insert a horizontal line?

Add three or more asterisks (\*), hyphens (-), or underscores (\_) on a line, optionally separated by spaces. Example:

\*\*\*

\---

\----

![](/files/c3Awz8NlP1mcHoLSblDH)

### How to create clickable links?

Create a link by placing the link text in brackets, followed immediately by the URL in parentheses. Example:

\[text to link]\(<http://example.com>)

![](/files/4rgQetFTTJ5NKJfscAZH)

### How to create tables?

You can create tables using either the Text or Table widget. To create one through the Text widget, use vertical bars | to structure the cells and hyphens to separate the header. Example:

\| Header | Column 1 | Column 2 | Column 3 |

\|:------ |:-------- |:--------:| --------:|

\| 1. Row | is | is | is |

\| 2. Row | left | nicely | right |

\| 3. Row | aligned | centered | aligned |

![](/files/vPORspaxdF0raDU6bRKv)

To create one using the Table widget, simply gp back to the General tab, select “Table” and go the Setup tab to customize it.

![](/files/znxF0ij5qT6IBO8KqP9t)

<figure><img src="/files/QdFMRailD7GmpgGXYmvv" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Best Practices

* Use short, clear titles
* Separate long sections with horizontal lines
* Prefer lists for operational information
* Avoid excessive formatting — keep it simple
* Use tables to define rules, criteria, and values
* Use images only when essential
  {% endhint %}

### Read also

* [Telling stories with Custom Dashboards](broken://pages/873aa0a32e7f3fef9fb27647594dd2be106e6f65)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ask.birdie.ai/voice-of-customer/dashboards-and-reporting/dashboard-widgets/text-widget.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
