> For the complete documentation index, see [llms.txt](https://docs.opensoutheners.com/oss/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opensoutheners.com/oss/readme.md).

# Developer Platform

Welcome to your team’s developer platform

<h2 align="center">Open Southeners Documentation</h2>

<p align="center">Documentation for our open source libraries, tools, and community projects.</p>

<p align="center"><a href="https://github.com/open-southeners" class="button primary">Browse projects</a> <a href="https://opensoutheners.com/" class="button secondary">Website</a></p>

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><h4><i class="fa-leaf">:leaf:</i></h4></td><td><strong>For users</strong></td><td>Discover projects, installation guides, usage examples, and configuration docs.</td><td><a href="broken://spaces/qcBJT0R8u1uowNSEVcOO">Broken link</a></td><td><a href="https://content.gitbook.com/content/1Xlr4iX6VdOsn5C0WbDe/blobs/Bal4XE4v7RvrgLcT5WML/no-code.jpg">no-code.jpg</a></td></tr><tr><td><h4><i class="fa-cubes">:cubes:</i></h4></td><td><strong>For contributors</strong></td><td>Learn how to contribute, report issues, follow standards, and submit PRs.</td><td><a href="broken://spaces/qcBJT0R8u1uowNSEVcOO">Broken link</a></td><td><a href="https://content.gitbook.com/content/1Xlr4iX6VdOsn5C0WbDe/blobs/UBwsmhuf6bhGsi2mOc9F/hosted.jpg">hosted.jpg</a></td></tr><tr><td><h4><i class="fa-terminal">:terminal:</i></h4></td><td><strong>For maintainers</strong></td><td>Release process, documentation standards, versioning, and project governance.</td><td><a href="broken://spaces/naeVnhgTRnhyui5Y0UO3">Broken link</a></td><td><a href="https://content.gitbook.com/content/1Xlr4iX6VdOsn5C0WbDe/blobs/mizyAiD4yh8zfpERuzJl/api-reference.jpg">api-reference.jpg</a></td></tr></tbody></table>

<h2 align="center">Join our community</h2>

<p align="center">Join our Discord community or create your first PR in just a few steps.</p>

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th></th><th></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><h4><i class="fa-discord">:discord:</i></h4></td><td><strong>Discord community</strong></td><td>Join our Discord community to post questions, get help, and share resources with other developers.</td><td><a href="https://discord.gg/2DVVWy5FwC" class="button secondary">Join Discord</a></td><td></td></tr><tr><td><h4><i class="fa-github">:github:</i></h4></td><td><strong>GitHub</strong></td><td>Our product is 100% open source and built by developers just like you. Head to our GitHub repository to learn how to submit your first PR.</td><td><a href="https://github.com/open-southeners" class="button secondary">Submit a PR</a></td><td></td></tr></tbody></table>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.opensoutheners.com/oss/readme.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 `build a script that syncs our docs to a CMS` 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.