> For the complete documentation index, see [llms.txt](https://code-for-philly.gitbook.io/partnerships/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://code-for-philly.gitbook.io/partnerships/defining-the-partnership.md).

# Defining the partnership

Partnerships at Code for Philly help volunteers stay connected with important issues in the city, mobilize where support is needed, and ensure we can provide regular space for collaboration.

The first step of defining a partnership is deciding what kind of opportunity it might open up:

1. **Relationship** - you want to raise awareness around a compelling non-profit. They may not need many volunteers yet, but an introduction to Code for Philly leadership, or a single volunteer to coordinate sharing their mission at a meetup.
2. **Active Project** - what people often associate with Code for Philly. This is when volunteers support a project run by a partner. Depending on the project's needs, it could rally many volunteers, or only a single volunteer.
3. **Sponsorship** - sponsors enable Code for Philly to facilitate volunteer work. This occurs through hosting weekly space for presentations, or providing financial sponsorship for larger events.


---

# 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://code-for-philly.gitbook.io/partnerships/defining-the-partnership.md?ask=<question>&goal=<endgoal>
```

`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.