> For the complete documentation index, see [llms.txt](https://docs.ideamarket.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ideamarket.io/navigating-the-app/how-to-make-a-good-post.md).

# How to make a good post

### A good post is also a useful citation.

Unless you're famous, your best bet at getting a lot of people to rate your post is attracting citations, so that your post becomes a default reference point for that topic across the entire ecosystem.

Tips:

* **Write in complete sentences.** A complete sentence provides context and expresses a point of view, rather than just saying `alien video https://youtube.com/9jf209mm2me....`
* **Limit each post to 1 main idea.** If a post has multiple ideas in it, it will be less useful as a citation because people might only want to cite half of your post, and won't be able to.
* **If your post contains a link, provide context.** Summarize the link so people know what it's about without having to click it.
* **Think of posts as "nodes" rather than "replies."** Even if you're replying to someone else's post, your post will also appear by itself without any context. If your post doesn't make sense by itself without context, it probably won't attract many ratings.


---

# 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.ideamarket.io/navigating-the-app/how-to-make-a-good-post.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.