# Markdown

The complete documentation is written in markdown code. Here are some examples:

### Headings

| Markdown              | HTML                       | Rendered Output          |
| --------------------- | -------------------------- | ------------------------ |
| # Heading level 1     | \<h1>Heading level 1\</h1> | <h2>Heading level 1</h2> |
| ## Heading level 2    | \<h2>Heading level 2\</h2> | <h3>Heading level 2</h3> |
| ### Heading level 3   | \<h3>Heading level 3\</h3> | <h4>Heading level 3</h4> |
| #### Heading level 4  | \<h4>Heading level 4\</h4> | **Heading level 4**      |
| ##### Heading level 5 | \<h5>Heading level 5\</h5> | **Heading level 5**      |

***

### Images

Screenshots can also be submitted. For uniformity, we may replace graphics with our own.

The images are always stored in the same folder level in a `.images` directory. They are then linked in this way:

```markdown
![Test image](https://github.com/mainIine/foe-helper-docs/raw/master/en/guide/.images/app48.png)
```

Rendered

![Test image](https://github.com/mainIine/foe-helper-docs/raw/master/en/guide/.images/app48.png)

***

### Links

Links are always converted automatically and do not require any extra code.

***

### Hints

Hints can created by the following syntax:

```markdown
<div data-gb-custom-block data-tag="hint" data-style='info'>

Hello world

</div>
```

These values are possible: `info`, `success`, `danger` & `warning`

Examples:

{% hint style="info" %}
Info hint
{% endhint %}

{% hint style="success" %}
Success hint
{% endhint %}

{% hint style="danger" %}
Danger hint
{% endhint %}

{% hint style="warning" %}
Warning hint
{% endhint %}

***


---

# 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://docs.foe-helper.com/francais/guide/markdown.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.