> For the complete documentation index, see [llms.txt](https://docs.hablla.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hablla.com/hablla-docs-en/contribute-with-us.md).

# Contribute with us

At Hablla, we believe that knowledge building is collaborative.

If you missed any explanation, use case, or want to suggest improvements to our documentation, use the form below to submit your request.

The documentation of **Hablla** is constantly evolving. Our ecosystem is **comprehensive** and is always expanding, and not all features and use cases are documented yet.

To help us prioritize the most relevant areas, we provide a form where you can request **new content, improvements to existing materials or examples of use cases**.\
Your contribution guides our editorial roadmap and ensures that the most in-demand topics receive priority in the documentation.

Your contribution helps us keep the **Hablla Documentation** always up to date, practical and aligned with the real needs of the ecosystem.

> 💡 **Help improve our documentation**\
> Click the button below to open the request form:
>
> [![Abrir formulário](https://img.shields.io/badge/Hablla-Formul%C3%A1rio-blue?style=for-the-badge)](https://forms.hablla.com/68aaeb0866eab34182c38700/)


---

# 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.hablla.com/hablla-docs-en/contribute-with-us.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.
