> For the complete documentation index, see [llms.txt](https://docs.voidline-development.ct.ws/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.voidline-development.ct.ws/welcome.md).

# 👋 Welcome

Welcome to the official documentation hub for Voidline Development™ — your home for powerful tools, scripts, and integrations built for modern developers and communities.

Here, you'll find everything you need to:

* ✅ Set up and use our products
* 🛠️ Troubleshoot issues
* 🚀 Learn best practices
* 🧠 Discover tips, examples, and advanced guides

Whether you're just getting started or deep-diving into advanced features, these docs are built to support you every step of the way.

If you ever get stuck or need help:

* Visit our [Support Server](https://voidline-development.ct.ws/discord)
* Check out our [Main Site](https://voidline-development.ct.ws)
* Review our [Terms of Service](https://voidline-development.ct.ws/tos) & [Privacy Policy](https://voidline-development.ct.ws/privacy)

Happy building!\
**– The Voidline Development™ Team**


---

# 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.voidline-development.ct.ws/welcome.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.