# Application documentation
{% stepper %}
{% step %}
### Creation of documentation
In the **Documentation** use the button **Add documentation**, and then enter the name of the documentation being created.
The entry should contain a business description of the change - aimed at non-technical people and people interested in the product from a business perspective.
Figure 1. Documentation creation window
{% endstep %}
{% step %}
### Editing documentation
To edit existing documentation, go into the documentation and click the button **Edit documentation** .
The editing window is divided into a creation and preview section. Between the screens there is a bar that allows you to change the width of both sections.
Figure 2. Documentation editing window
{% endstep %}
{% step %}
### Creating entries — markdown syntax
Entries are created using the [markdown](https://www.markdownguide.org/basic-syntax/)tags. The documentation window contains a markdown editor with preview.
Sample documentation using markdown (sample material showing various syntax elements):
{% code fullWidth="false" expandable="true" %}
```markdown
# Markdown syntax guide
## Headers
# This is a Heading h1
## This is a Heading h2
###### This is a Heading h6
## Emphasis
*This text will be italic*
_This will also be italic_
**This text will be bold**
__This will also be bold__
_You **can** combine them_
## Lists
### Unordered
* Item 1
* Item 2
* Item 2a
* Item 2b
### Ordered
1. Item 1
2. Item 2
3. Item 3
1. Item 3a
2. Item 3b
## Images
## Links
You may be using [Markdown Live Preview](https://markdownlivepreview.com/).
## Blockquotes
> Markdown is a lightweight markup language with plain-text-formatting syntax, created in 2004 by John Gruber with Aaron Swartz.
>>
>> Markdown is often used to format readme files, for writing messages in online discussion forums, and to create rich text using a plain text editor.
## Tables
| Left columns | Right columns |
| ------------- |:-------------:|
| left foo | right foo |
| left bar | right bar |
| left baz | right baz |
## Blocks of code
```
{% endcode %}
{% hint style="info" %}
The editor supports creating and previewing markdown in real time. Between the editor and the preview you can adjust the width using the bar.
{% endhint %}
{% endstep %}
{% step %}
### Managing documentation artifacts
For a documentation artifact you can:
* view the version history,
* create a copy of the artifact,
* download it to disk.
It is enough in the **Documentation** window to click the context menu of a given artifact.
Figure 3. List of application documentation with the context menu of one of the artifacts.
{% endstep %}
{% endstepper %}
---
# 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.eximee.com/documentation/documentation-en/budowanie-aplikacji/aplikacja-biznesowa/dokumentowanie-aplikacji.md?ask=
```
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.