> 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/community/get-involved.md). # Get involved Join the World IA Day LOCATION volunteer team! Help organize our information architecture community event and connect with local practitioners. Our events are made possible by passionate volunteers, knowledgeable speakers, and dedicated organizers who contribute their time and expertise to advance the practice of IA. {% hint style="info" %} Some content ideas for the Get involved page. Feel free to make this your own. {% endhint %} * What volunteer opportunities typically exist for World IA Day space.vars.LocationName? * Event planning roles? * Day-of-event support? * Year-round activities? * Content creation/social media? * What's the typical time commitment you want to communicate for different roles? * Do you have an application process or is it more informal "email us" approach? * What skills or experience do you look for in volunteers? Or do you welcome everyone regardless of experience? * Are there other ways to get involved beyond organizing the annual event? Are there local meetups, ongoing community activities, etc. where people could get involved with? * What benefits or value do volunteers get from participating? Networking, experience, community, etc. --- # 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/community/get-involved.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.