> For the complete documentation index, see [llms.txt](https://desmoines.worldiaday.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://desmoines.worldiaday.org/events/template-des-moines-yyyy.md).

# \[TEMPLATE] Des Moines YYYY

{% hint style="warning" %}
Event ended
{% endhint %}

We are planning our celebration! If you would like to volunteer or sponsor, please get in touch.

## Date and time

Saturday, March 8, 2026

## Location

VENUE NAME\
VENUE ADDRESS

Map directions | Venue details

STATIC MAP IMAGE

***

## This year's theme

Local interpretation of this year's theme

***

## Speakers

{% hint style="info" %}
**Tip:** You can turn a table into a grid using the block options to hide field names, setting cover image and target link. 
{% endhint %}

<table><thead><tr><th>Name</th><th data-type="content-ref">Link</th><th>Company</th></tr></thead><tbody><tr><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td></tr></tbody></table>

***

## Agenda

| <p>8:30 am - 9:25 am<br>Registration & Networking</p> |
| ----------------------------------------------------- |
| <p>9:30 am - 9:55 am<br>Opening Remarks</p>           |
| <p>10:00 am - 12:00 pm<br>Morning Presentations</p>   |
| <p>12:00 pm - 1:00 pm<br>Lunch</p>                    |
| <p>1:00 pm - 3:25 pm<br>Afternoon Presentations</p>   |
| <p>3:30 pm<br>Closing Remarks</p>                     |

***

## Program schedule

### `HH:MM am/pm`  - Talk title - Speaker(s)

Session description

Presented by SPEAKER NAME with link to bio

<details>

<summary>About SPEAKER NAME</summary>

Author bio

{% hint style="info" %}
Tip: You can create bio pages under Community or you can put bios in a collapsible container.
{% endhint %}

</details>

***

## Sponsors supporting LOCATION YYYY

{% hint style="info" %}
You can turn the table into a card grid layout. Remove the labels and hide the fields that don't need to be exposed.
{% endhint %}

<table data-column-title-hidden data-view="cards" data-full-width="false"><thead><tr><th>NAME</th><th data-hidden data-card-target data-type="content-ref">LINK</th></tr></thead><tbody><tr><td></td><td></td></tr><tr><td></td><td></td></tr><tr><td></td><td></td></tr></tbody></table>

***

## Our team

<table data-view="cards"><thead><tr><th>Name</th><th>Role</th><th data-hidden data-card-target data-type="content-ref">Link</th></tr></thead><tbody><tr><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td></tr></tbody></table>


---

# 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://desmoines.worldiaday.org/events/template-des-moines-yyyy.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.