> For the complete documentation index, see [llms.txt](https://docs.correlaid.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.correlaid.org/community/doing-a-project.md).

# Doing a project

It is also possible to carry out projects at the local level via CorrelAid. However, it is important to us that the projects meet the criteria we set for our own projects. Hence, please make sure to check this guide when deciding on whether to do a project with a potential partner organisation:

{% content-ref url="/pages/-MYOt9-X7PRSL5iHoKmK" %}
[When do we do a project? When not?](/projects/project-decision-guide.md)
{% endcontent-ref %}

Also make sure to check out the [toolbox](broken://pages/-MMKcyJY6etdpq45QfyK) for more resources and the [project coordination subpages](/projects/project-coordinators.md) for more information on how to organize your own project.


---

# 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://docs.correlaid.org/community/doing-a-project.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.