> For the complete documentation index, see [llms.txt](https://docs.eximee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/biblioteka-komponentow-bazowych/4-tresci/tresc-textcontent/edytor-tresci.md).

# Content editor

## Preliminary information

To create a new one or edit an existing one, go to the module **Library** and select the tab **Content**. A list of artifacts of this type will be displayed. From this view, you can create new content, review the history of saved versions, or edit an existing content artifact.

![Figure 1. Window with a list of content and the context menu of one of the artifacts](https://content.gitbook.com/content/2CssJT0zIo4SJQLbSZ6l/blobs/pwdBaeku3nl0j8G9ubNm/25k_files/Zaznaczenie_1608.png)

## Preview / Edit

After opening a specific piece of content, you can start editing the artifact and save its new version. Available translations are displayed on the left, and on the right the HTML code preview and the final appearance of the content (rendered HTML code).

![Figure 2. Content editing](https://content.gitbook.com/content/2CssJT0zIo4SJQLbSZ6l/blobs/JFAvkOD7lyVMeJTdA9so/25k_files/image2025-9-2_14-55-36.png)

More information about the artifact **Content** and the base component **Formatted content** in [Formatted content - TextContent](/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/biblioteka-komponentow-bazowych/4-tresci/tresc-formatowana-textcontent.md).


---

# 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.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/biblioteka-komponentow-bazowych/4-tresci/tresc-textcontent/edytor-tresci.md?ask=<question>&goal=<user_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.