# Submit Feedback
There are different ways to submit feedback on the Umbraco Documentation, whether it's about a single article or the platform as a whole. Your input helps us improve and prioritize what matters most to the community.
This article gives you an overview of the different feedback channels and how to use them.
## Submit Feedback on an Article
On the right-hand side of every article, you'll find an option to submit feedback directly related to that article.
Rate the documentation by sharing whether an article was helpful.
{% hint style="success" %}
Sharing your feedback helps the team at Umbraco HQ provide better material across the products.
The feedback is used when determining which articles need to be reviewed by the documentation team at Umbraco HQ.
{% endhint %}
## Submit a GitHub Issue
The [Issue Tracker](https://github.com/umbraco/UmbracoDocs/issues) is a way to keep track of ideas, issues with wrong or outdated documentation, and discussions with contributors.
Here are a few examples of when to create an issue:
* You are looking for a specific piece of information, but can't find it.
* You've found a broken link in one of the articles, but don't know how to fix it.
* An article contains outdated or incorrect information, and you don't have time or knowledge to submit a PR.
* You would like to propose a new section or discuss improvements to existing documentation.
### Creating an Issue
1. Go to the [Issue Tracker on GitHub](https://github.com/umbraco/UmbracoDocs/issues).
2. Select **New Issue**.
3. Fill out the form, answering the questions to explain your suggestion or problem clearly.
4. Submit the issue.
---
# Agent Instructions: 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:
```
GET https://docs.umbraco.com/contributing/documentation/getting-started/issues.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.