> For the complete documentation index, see [llms.txt](https://handbook.developerdao.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.developerdao.com/readme.md).

# Welcome Developer DAO

These docs are a guide for members and non-members alike. If you want to understand what the DAO does, how to get involved or how to join, you're in the right place.

## What is Developer DAO?

We are a developer-owned and governed community learning and building for Web3.

### What do we do?

We provide opportunities and incentives for builders of all levels to learn about Web3 and build projects that impact the world.

### What is this handbook?

Your guide to everything Developer DAO.

Communities, and DAOs in particular, can be confusing and overwhelming, so we aim for this handbook to make it easy to understand and find your way in the DAO.

### First Steps...

Now you know a little bit about us, you're ready to take your [First Steps](/getting-started-in-the-dao/first-steps.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://handbook.developerdao.com/readme.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.
