> For the complete documentation index, see [llms.txt](https://help.maearth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.maearth.com/resources-for-land-stewards/project-profile/project-name.md).

# Project Name

What makes a strong project name?

<figure><img src="https://2063698258-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgHG6xewZ2558xKhpLEAa%2Fuploads%2Fhu8cWKbTnFlLfyTbVnvq%2FScreenshot%202026-10-02%20at%205.44.43%E2%80%AFPM.png?alt=media&amp;token=aeb8f369-65c7-40ca-bbbf-055b51f97611" alt=""><figcaption></figcaption></figure>

Your project name appears everywhere: your campaign page, search results, and social media shares. We encourage you to make it clear and easy to remember.

#### Strong project names are:

* **Clear.** Communicate what you're doing. (ie. "Kilifi Mangrove Restoration" not "Blue Carbon Initiative Phase 2")
* **Specific.** Include the project location or a key detail. (ie. "Oaxaca Rainwater Harvesting" not "Water Project")
* **Concise.** Keep it under 60 characters. (ie. "Planting Food Forests in the Peruvian Amazon" not "Comprehensive Multi-Year Reforestation and Agroforestry Initiative in the Peruvian Amazon Basin")
* **Memorable.** Easy to say and remember. (ie. "Youth Community Garden in Bogotá, Colombia" not "RCFN-2026-A")
* **Genuine.** Avoid generic phrasing and cliche (ie. **not** "Saving the World One Tree at a Time")

**Here's a formula that can work to create your project name:**

\[What you're doing] + \[Where] or \[Who's leading/benefiting]

* Mangrove Restoration + Kilifi = "Kilifi Mangrove Restoration"
* Rainwater Harvesting + Oaxaca Community = "Oaxaca Community Rainwater Systems"
* Food Forests + Indigenous + Ecuador = "Planting Indigenous Food Forests in Ecuador's Amazon Basin"

You don’t have to follow this formula; feel free to get creative.

#### **Your project name is also your crowdfudning campaign title. It is helpful if the name is shareable, something your supporters will be excited to share with their own networks.**

<br>


---

# 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://help.maearth.com/resources-for-land-stewards/project-profile/project-name.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.