> For the complete documentation index, see [llms.txt](https://docs.oscafrica.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oscafrica.org/community/chapters.md). # Chapters An Open Source Community Africa chapter is a community closer to home. It typically consists of a group of people coming together to organize and facilitate meetups, creating an environment of support in possible areas of challenge while following the OSCA Code of Conduct. Our goal is to increase the rate of credible contributions by African software developers, designers, writers, and everyone involved in the sphere of technology to open source projects both locally and globally, changing Africans' perception from just the billion users to the NEXT BILLION CREATORS. An OSCA chapter lead represents a global network of open-source enthusiasts and is responsible for growing and supporting vibrant local OSCA communities in Africa. {% embed url="" %} Learn more about the OSCA community. {% endembed %} --- # 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.oscafrica.org/community/chapters.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.