> For the complete documentation index, see [llms.txt](https://zefyr-editor.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zefyr-editor.gitbook.io/docs/faq.md).

# FAQ

## Q: Are Notus documents compatible with Quill documents?

Short answer is no. Even though Notus uses Quill Delta as underlying representation for its documents there are at least differences in attribute declarations. For instance heading style in Quill editor uses "header" as the attribute key, in Notus it's "heading".

There are also semantic differences. In Quill, both list and heading styles are treated as block styles. This means applying "heading" style to a list item removes the item from the list. In Notus, heading style is handled separately from block styles like lists and quotes. As a consequence you can have a heading line inside of a quote block. This is intentional and inspired by how Markdown handles such scenarios. In fact, Notus format tries to follow Markdown semantics as close as possible.


---

# 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://zefyr-editor.gitbook.io/docs/faq.md?ask=<question>&goal=<endgoal>
```

`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.