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

# Philadelphia 2027

World IA Day Philadelphia 2027

{% 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 6, 2027

## 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="files">Photo</th><th data-type="content-ref">Link</th><th>Company</th></tr></thead><tbody><tr><td></td><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td><td></td></tr><tr><td></td><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 Philadelphia 2027

{% 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-view="cards" data-full-width="false"><thead><tr><th>NAME</th><th data-card-cover data-type="files">LOGO</th><th 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>

***

## Our team

<table><thead><tr><th>Name</th><th data-type="files">Profile picture</th><th data-type="content-ref">Link</th><th>Role</th></tr></thead><tbody><tr><td></td><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td><td></td></tr></tbody></table>

***

## Our supporters

\[Display sponsor logos with links - can be organized by sponsorship level]

*Interested in sponsoring? View our sponsorship opportunities →*


---

# 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://philadelphia.worldiaday.org/events/philadelphia-2027.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.