> For the complete documentation index, see [llms.txt](https://www.tvrename.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.tvrename.com/help-and-support/what-can-i-do-to-help.md).

# What can I do to help?

Another good question! So far we’ve only really talked about us helping you, let's talk about you helping us.

The team that looks after TV Rename is **very** small, just one core developer and one guy looking after the website. They volunteer their time and expertise to bring you a tool that works to enhance your television entertainment.

Any time you can donate to help out is very much appreciated, whether you can code in C# using .NET or spot an HTML/CSS markup issue or a simple spelling mistake or grammatical error at 100m or even just keep an eye on the forum and help out when others get stuck, it all helps improve what we think is already a great tool.

Seriously, if you can help out please let us know (in [the forum](https://groups.google.com/forum/#!forum/tvrename))!


---

# 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://www.tvrename.com/help-and-support/what-can-i-do-to-help.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.
