> For the complete documentation index, see [llms.txt](https://monitoring.toolkit.citiobs.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://monitoring.toolkit.citiobs.eu/readme/contributions-and-feedback.md). # Contributions & Feedback ### Content Contributions The easiest way to contribute is via a GitHub issue and, if you can, a Pull request. This process can be scary at first, but it's the way it's done in the *open source* community. {% hint style="info" %} Check the following [documentation on pull requests](https://docs.github.com/en/pull-requests) and learn more about [issues](https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/creating-an-issue). {% endhint %} ### Feedback We welcome your feedback to this toolkit via email or on [Github](https://github.com/CitiObs/environmental-monitoring-toolkit). You can also use the feedback buttons on the Gitbook interface. #### Via Gitbook You will find the following feedback icons on the page.

Feedback interface

We really appreciate the feedback, specially if you can add some additional context for us to improve:

Add some additional context!

#### Via GitHub / email You can use this template to send us comments on a more structured way. * **I'm submitting a …** This is the category of your feedback. You need to choose whether you are reporting a problem you found or requesting that new content be added. This helps the team understand the fundamental nature of your submission right away. * **problem report** You found something that isn't working correctly, is confusing, or seems wrong. * **new content request** You think something is missing or could be added to make the toolkit better. * **What is the current behavior?** This is where you describe the situation as it is now. * If you are submitting a problem report, you should explain what you are currently seeing or experiencing that is incorrect or problematic. * If the current behaviour is a problem, please provide the details of where you found it (which page and section). This is crucial for problem reports as it helps the team locate the exact part of the toolkit you are referring to. * **What would you improve?** This is where you propose your solution or suggestion. You explain what you think should be changed or added. * **What is the motivation / use case for changing the behavior?** This explains why your suggestion is important or how it would be used. This provides context for your feedback and helps the team understand the benefit of implementing your proposed change or adding the new content. * **Other information** This is a space for any additional details that might be relevant but don't fit neatly into the categories above. --- # 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://monitoring.toolkit.citiobs.eu/readme/contributions-and-feedback.md?ask=&goal= ``` `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.