> 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/getting-started-in-the-dao/attend-our-events.md).

# Attend our Events

{% hint style="info" %}
Most of our events are open to everyone. However, some are held in discord and only available to members. This is made clear below, and also using tags on luma using `Members only` or `Open to all` tags.
{% endhint %}

## Where to find our events?

Our event calendar is hosted on Luma.

When you RSVP an event to an event on Luma, you'll get an event added to your diary. Remember to subscribe to our event notifications by clicking the "Subscribe" button on that page.

{% embed url="<https://lu.ma/developer-dao-events>" %}

### Adding events to your calendar

You can access the calendar for our events using the link below. &#x20;

You can also add a feed of our events to your Google, Outlook or Apple Calendar by clicking the 📶 icon on the link above.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://handbook.developerdao.com/getting-started-in-the-dao/attend-our-events.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.