> For the complete documentation index, see [llms.txt](https://meetbit.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://meetbit.gitbook.io/docs/others/github-markdown.md).

# GitHub Markdown

MeetBit uses GitHub's version of Markdown to style several customer-facing elements of the platform. This section is a brief guide outlining the basics of using GitHub Markdown. For more in-depth knowledge, you can refer to the [official Github Markdown documentation](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax).

{% hint style="warning" %}
Contrary to GitGub's Markdown version, **MeetBit does not permit the use of HTML code in any of its fields** that employ Markdown.
{% endhint %}

{% hint style="info" %}
Markdown is commonly used along with [Liquid Templating](/docs/others/liquid-templating.md). In these cases, Liquid is applied first before Markdown processing takes place.
{% endhint %}

## Headings

Headings are denoted by the hash sign (`#`). The number of hash signs denotes what level of heading it is.

```markdown
# Heading 1
## Heading 2
### Heading 3
```

## Styling Text

Markdown allows you to stylize your text by making it bold, italic, and strikethrough.

<pre class="language-markdown"><code class="lang-markdown"><strong>**This is bold**
</strong><strong>*This is italic**
</strong></code></pre>

## Links

You may include clickable links to external URLs through Markdown.

```markdown
You may click the link [here](https://meetbit.io).
```

## Reference

* [Official Github Markdown Documentation](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)


---

# 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://meetbit.gitbook.io/docs/others/github-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.