> For the complete documentation index, see [llms.txt](https://cesena.worldiaday.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cesena.worldiaday.org/home.md).
# Home
Celebrating Information Architecture in LOCATION since 2012
## Welcome to World IA Day Cesena
Il #Wiad, World Information Architecture Day, è la giornata internazionale dedicata all’architettura dell’informazione. In tutto il mondo la comunità globale di architettɜ dell’informazione si riunisce, per “celebrare e promuovere la crescita globale dell'architettura dell'informazione a partire dalle realtà locali, attraverso il confronto tra colleghi e la contaminazione di discipline diverse”.
💥Dal 2012 il Wiad anima le comunità di pratica sparse per il mondo, promuovendo talk e organizzando workshop e laboratori.
***
### 📅 World IA Day 2026 - 7 Marzo 2026
\[Brief description of this year's event and local interpretation of the global theme - 2-3 sentences]
View event details
***
#### Event history highlights
* [Cesena 2025](/events/cesena-2025.md): 7 e 8 Marzo 2025
* [Cesena 2024](/events/cesena-2024.md): 2 Marzo 2024
* [Cesena 2020](/events/cesena-2020.md): 22 feb 2020
***
### :e-mail: Contact & connect
**General inquiries:**
***
*World IA Day Cesena 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://cesena.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.