> For the complete documentation index, see [llms.txt](https://help.hippoly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.hippoly.com/using-hippoly/posts/create-post.md).
# Create post
Creating posts ara super easy. Apart from text your posts can contain images, files and polls. To create a post follow these steps
{% stepper %}
{% step %}
Navigate to `Posts` in the main menu.
{% endstep %}
{% step %}
Type your message in the input field at the top of the page.
Create post
{% endstep %}
{% step %}
To add an image, file, or poll to your post, simply use the buttons below the input field.
{% endstep %}
{% step %}
Finally click the `Send` button to share your post with your team.
{% endstep %}
{% endstepper %}
{% hint style="info" %}
Want to include a poll in your post? [Learn more about creating a poll in this article](/using-hippoly/polls/create-poll.md).
{% 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.hippoly.com/using-hippoly/posts/create-post.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.
