> 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/projects-and-opportunities/how-to-contribute-and-collaborate/submitting-project-ideas-and-proposals.md).

# Submitting Project Ideas and Proposals

At Urban Array, we believe in the power of our community to generate innovative ideas that drive change. If you have an idea for a project that aligns with our mission, we encourage you to submit a proposal. To do so, follow these steps:

1. Develop your idea: Define your project's objectives, scope, timeline, and any resources needed.
2. Create a project proposal: Write a detailed proposal outlining your project's goals, strategies, and expected outcomes. Include information on how it aligns with Urban Array's mission and values.
3. Submit your proposal: Share your proposal with our team for review and consideration. You can submit it through our website or by contacting us directly.
4. Await feedback: Our team will review your proposal and provide feedback or request additional information if needed. This process may take some time, so please be patient.
5. Get involved: If your proposal is approved, we'll work with you to establish the project within our community and help you recruit team members.

By getting involved in projects and opportunities, you can make a meaningful impact on our mission to create sustainable, equitable neighborhoods and contribute to the growth of our community.


---

# 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/projects-and-opportunities/how-to-contribute-and-collaborate/submitting-project-ideas-and-proposals.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.
