> For the complete documentation index, see [llms.txt](https://docs.imerit.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.imerit.net/labeling/labeling-editor-interface/markdown-labeling-editor.md).
# Markdown Labeling Editor
Overview of the Markdown labeling editor in Ango Hub
Ango Hub provides a labeling editor with which Markdown files can be annotated.
{% hint style="info" %}
This article will exclusively go over Ango Hub’s Markdown labeling interface. Features common to all labeling editors are instead [explained here](/labeling/labeling-editor-interface.md).
{% endhint %}
## Overview
### Supported File Types
The markdown labeling editor supports text assets with the following file extensions:
* .md
### Supported Labeling Tools
The markdown labeling editor supports following labeling tools:
**Classifications**
* Radio
* Checkbox
* Single-Select Dropdown
* Multi-Select Dropdown
* Single-Select Tree
* Multi-Select Tree
* Text
**Relations**
* Single Relation
* Group Relation
### Top Bar
### Model Plugins
Click on the "Model Plugins" button to open a list of [model-type plugins](/plugins/plugin-developer-documentation.md) available in your organization.
If a [default preset](/plugins/introduction-to-plugins/plugin-configuration-and-preset-management.md) has been set for the plugin, the button will be clickable, and clicking on it once will run the plugin on the current asset with the default settings.
Clicking on the three dots next to the model name will open the Model Run Dialog, allowing you to customize the plugin's run settings and to run the plugin on the current asset with settings of your choice.
### KaTeX and LaTeX Rendering
The *Enable KaTeX Rendering* button will render any mathematical LaTeX markup visible in the asset into formatted mathematical notation.
The *Compile as LaTeX* button will take the text content of the current asset and treat it as LaTeX markup, then attempt to compile the document. If compilation was successful, it will display the resulting PDF. Through the option toggles, you may ask Ango Hub to wrap the text with a document environment (i.e. `\begin{document}` and `\end{document}`) and to add a document-type class.
## How to Annotate Markdown
In Markdown assets, only classifications are available.
Answer classifications embedded in the Markdown directly in the asset. Any classification that is not embedded appears in the *Classifications* panel on the left sidebar. When every classification is embedded and there are no objects to display, Ango Hub hides the left sidebar to give the asset more space.
When done, click on *Submit* on the top-right corner of the screen.
### Keyboard Shortcuts
A full list of keyboard shortcuts is available by clicking on the *Keyboard* button on the right side of the top bar:
### Further reading
{% content-ref url="/pages/-MjiniaaX8Bc-1CsxFDT" %}
[Audio Labeling Editor](/labeling/labeling-editor-interface/audio-labeling-editor.md)
{% endcontent-ref %}
{% content-ref url="/pages/-Mk6DvRXUK6-NIvfsXeq" %}
[Image Labeling Editor](/labeling/labeling-editor-interface/image-labeling-editor.md)
{% endcontent-ref %}
{% content-ref url="/pages/-Mk6GBzBlgn96o0VYkRi" %}
[PDF Labeling Editor](/labeling/labeling-editor-interface/pdf-labeling-editor.md)
{% endcontent-ref %}
{% content-ref url="/pages/-Mjifco2debe91gXbTS1" %}
[Labeling Editor Interface](/labeling/labeling-editor-interface.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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.imerit.net/labeling/labeling-editor-interface/markdown-labeling-editor.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
