> 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/about/guidelines.md).

# Branding Guidelines

## Naming guidelines

1. The official name for the organization is "Open Source Community Africa" with its acronym as OSCA.
2. When writing the the official name for the organization, the first letter of each word should be *capitalized*.
3. The official acronym for the organization should be spelt using *UPPERCASE* only.

### Do’s

* Refer to the community as "OSCA".
* Describe the community as "OSCA" stands for "Open Source Community Africa and is a community of Open source advocates and contributors across Africa.".

### Don’t:

* Refer to the community as "Open Source Africa" or "Open Source Community" instead of the acronym "OSCA".

## Chapter naming guideline

### Do's

* Each local OSCA chapter must be named as "OSCA (Location)".
* Name your chapter with a “Location” that is a city (e.g. Lagos, Port Harcourt)Refer to your chapter as "OSCA (Location)"

### Don’t

* Refer to your chapter as a “Open Source Community (Location),” "Open Source Africa (Location)" or "Open Source (Location)."
* Name your chapter with a “Location” that is a country or continent (e.g. Ghana, South-Africa, Africa).


---

# 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/about/guidelines.md?ask=<question>&goal=<user_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.