> For the complete documentation index, see [llms.txt](https://providence.worldiaday.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://providence.worldiaday.org/home.md).
# Home
Celebrating Information Architecture in LOCATION since 2012
## Welcome to World IA Day Providence
World Information Architecture Day has been celebrated in Providence since 2024, bringing together information architects, UX designers, content strategists, and digital professionals to explore the latest trends and practices in information architecture.
***
### 📅 World IA Day 2026 - March 7, 2026
\[Brief description of this year's event]
> 💡 **New to IA?** Don't worry! Our event welcomes practitioners at all levels, from curious newcomers to seasoned practitioners and academics.
View event details
***
#### Event history highlights
* **2025:** Challenges of Change
* **2024:** First World IA Day in Providence
[View our complete event history](/events/all-events.md) →
***
### 🌟 What makes WIAD Providence special
> *"\[Quote from past attendee or organizer about what makes your location unique]"*
>
> — \[Attribution]
***
### :e-mail: Contact & connect
**General inquiries:** \
**Sponsorship:** \[LINK]\
**Speaking opportunities:** \[LINK]
***
*World IA Day Providence is part of the global World Information Architecture Day celebration.* [*Learn more about World IA Day worldwide*](https://www.information-architecture.world/worldiaday) *→*
---
# 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://providence.worldiaday.org/home.md?ask=&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.