> 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/projects.md). # Projects - [A short project coordinator guide](https://docs.correlaid.org/projects/short-coordinator-guide.md): This page is supposed to give people who are not overly familiar with Data4Good project coordination at CorrelAid a starting point. - [The Ethics Questionnaire and its Companion Document](https://docs.correlaid.org/projects/the-ethics-questionnaire-and-its-companion-document.md): Let us guide you in having a close look at your nascent project. Use the Questionnaire and its Companion Document below to identify the most relevant questions to answer or to pass them on to us! - [Project coordination](https://docs.correlaid.org/projects/project-coordinators.md): This section explains how CorrelAid projects are coordinated and describes the relevant processes. The content is relevant for project coordinators and project leads. - [CorrelAid Data4Good projects](https://docs.correlaid.org/projects/project-coordinators/data4good-projects.md) - [Scoping & Call for Applications](https://docs.correlaid.org/projects/project-coordinators/scoping.md) - [Team selection](https://docs.correlaid.org/projects/project-coordinators/team-selection.md) - [Onboarding](https://docs.correlaid.org/projects/project-coordinators/onboarding.md) - [Kickoff](https://docs.correlaid.org/projects/project-coordinators/kickoff.md) - [Project work](https://docs.correlaid.org/projects/project-coordinators/project-work.md) - [Handover](https://docs.correlaid.org/projects/project-coordinators/handover.md) - [Documentation](https://docs.correlaid.org/projects/project-coordinators/documentation.md): What to document where. - [For the project team](https://docs.correlaid.org/projects/project-team.md) - [Best practices](https://docs.correlaid.org/projects/project-team/best-practices.md) - [General/Collaboration](https://docs.correlaid.org/projects/project-team/best-practices/collaboration.md) - [Dataviz / Reporting](https://docs.correlaid.org/projects/project-team/best-practices/dataviz-reporting.md): Collection of resources related to best practices for data visualization and reporting - [Python](https://docs.correlaid.org/projects/project-team/best-practices/python.md) - [R](https://docs.correlaid.org/projects/project-team/best-practices/r.md) - [Data privacy & security](https://docs.correlaid.org/projects/data-security-and-privacy.md) - [When do we do a project? When not?](https://docs.correlaid.org/projects/project-decision-guide.md): It is often difficult to say whether we do a project with an organisation. In this guide, we want to present the criteria that should guide that decision making process. - [FAQ](https://docs.correlaid.org/projects/faq.md) --- # 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/projects.md?ask=&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.