> For the complete documentation index, see [llms.txt](https://docs.dialogform.in/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dialogform.in/user-guide/how-to-write-markdown.md).

# How to write Markdown

This is how Markdown is defined in Wikipedia.

> **Markdown** is a lightweight markup language for creating formatted text using a plain-text editor.

Using just a few special characters, you can use a plain-text editor to generate formatted text with headings, lists, hyperlinks and more.

DialogForm supports Markdown in prompt messages, answer options and answer quick-responses.  Here's an example of how it looks in the editor and in the preview panel:

![](/files/J6SCpAkwW0Cdrw0GOfNX)

## What To Do

Instructions for all of the syntax that DialogForm supports can be found on the link below. \*\*Please ignore the "Images" and "Linking Images" sections on the page. DialogForm provides its own image uploading and insertion interface.

{% embed url="<https://www.markdownguide.org/basic-syntax>" %}

## What Next?

{% content-ref url="/pages/Kct34Y7KfgerCW1qlnk6" %}
[How to add images to Markdown](/user-guide/how-to-add-images-to-markdown.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.dialogform.in/user-guide/how-to-write-markdown.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.