> For the complete documentation index, see [llms.txt](https://docs.ninox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ninox.com/builder-hub/design-your-app/add-and-edit-data-fields-in-your-tables/all-data-fields/rich-text-html.md).
# Rich text (Html)
Use a **Rich text** field for content that should support formatted text.
This works well for descriptions, instructions, or content blocks that need more structure than plain text.
For the general settings all data fields have in common, see [Shared field settings](/builder-hub/design-your-app/add-and-edit-data-fields-in-your-tables/all-data-fields/shared-field-settings.md).
Field-specific settings for **Rich text** are:
:memo: **General**
* **Default value**:
* Enter a static formatted text directly into the field
* :code-simple: **Edit dynamic value** next to the field opens the logic editor where you can add or edit the logic for that setting. After you save the script, Ninox shows the first line of the script instead of the static value field. To switch back to a static value, click :xmark: **Remove dynamic value** on the right.
**Behavior**
* **Markdown**: controls whether the field supports Markdown formatting
In the **Rich text** editor, you can:
* undo or redo changes
* structure and format text
* adjust the text alignment
* discard or confirm changes
{% hint style="info" %}
Ninox stores rich text content as HTML and renders it in the **Rich text** field. Keep this in mind when you use scripts to update, read, or insert content in the field.
{% endhint %}
---
# 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.ninox.com/builder-hub/design-your-app/add-and-edit-data-fields-in-your-tables/all-data-fields/rich-text-html.md?ask=&goal=
```
`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.