> 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/community.md). # Community - [Membership Growth: Amplifying Our Collective Impact](https://docs.urbanarray.org/community/membership-growth-amplifying-our-collective-impact.md): Joining Urban Array, you're not just a member, but a crucial part of an inclusive collective dedicated to creating sustainable, equitable communities. Our strength lies in this collective effort. - [9 Hours a Week: Creating Waves](https://docs.urbanarray.org/community/9-hours-a-week-creating-waves.md) - [Communication Channels and Tools](https://docs.urbanarray.org/community/communication-channels-and-tools.md): Communication Channels and Tools for Effective Collaboration - [Ranks and Gamification](https://docs.urbanarray.org/community/ranks-and-gamification.md): Our rank system or Degrees is designed to foster growth, recognition, and empowerment within our community, while gamification adds an element of excitement and motivation to our collective journey. - [Member Degrees](https://docs.urbanarray.org/community/ranks-and-gamification/member-degrees.md): In our shared pursuit of building communities centered around empowerment, collaboration, and sustainability, Urban Array has devised a unique system known as Member Degrees. - [Unity Contributions](https://docs.urbanarray.org/community/unity-contributions.md): Unity Through Contribution: Harnessing Shared Responsibility and Investment - [Community Guidelines and Code of Conduct](https://docs.urbanarray.org/community/community-guidelines-and-code-of-conduct.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/community.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.