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

# Getting Started

- [How to Join Urban Array](https://docs.urbanarray.org/getting-started/how-to-join-urban-array.md): Welcome to Urban Array
- [Onboarding Checklist](https://docs.urbanarray.org/getting-started/how-to-join-urban-array/onboarding-checklist.md)
- [Roles Overview](https://docs.urbanarray.org/getting-started/roles-overview.md): Catalyze transformative change in communities through an ethos of unity, empowerment, and decentralized action. We nurture the power of collective effort.
- [Creative I (Phase 0)](https://docs.urbanarray.org/getting-started/roles-overview/creative-i-phase-0.md): Explore diverse roles within Urban Array's creative teams. They're instrumental in articulating our story and impact via visual content across platforms like LinkedIn and Instagram.
- [Community Activism & Outreach (Phase 0)](https://docs.urbanarray.org/getting-started/roles-overview/community-activism-and-outreach-phase-0.md): Roles that underpin Urban Array's mission, each contributing to community engagement, volunteer organization, advocacy efforts, and holistic community development. Sharing the impact of unity.
- [Building Projects (Phase 2)](https://docs.urbanarray.org/getting-started/roles-overview/building-projects-phase-2.md)
- [Financial Stewardship & Investment](https://docs.urbanarray.org/getting-started/roles-overview/financial-stewardship-and-investment.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.urbanarray.org/getting-started.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.