> For the complete documentation index, see [llms.txt](https://docs.aurelia.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aurelia.io/community-contribution/joining-the-community.md). # Joining the community Find out where our community hangs out and how to get connected. **Welcome to the Aurelia community!** 🎊 If you are looking to ask basic questions, [please visit our Discourse forum](https://discourse.aurelia.io/). For a more chat-like experience, our Aurelia 2 community also [hangs out on Discord](https://discord.gg/RBtyM6u). This documentation on Aurelia 2 is still preliminary, but that doesn't mean you can't jump in and join us in building the world's most-loved JavaScript framework. To get started working with us, please first read our [code of conduct](/community-contribution/code-of-conduct.md) and our [contributor guide](/community-contribution/contributor-guide.md). After that, if you want to contribute to the source code of Aurelia, its tools, or its plugins, have a read through [building and testing Aurelia](/community-contribution/building-and-testing-aurelia.md). If you'd like to contribute to our documentation, then please take a look at [writing documentation](/community-contribution/writing-documentation.md). We look forward to working together with you! --- # 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://docs.aurelia.io/community-contribution/joining-the-community.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.