> For the complete documentation index, see [llms.txt](https://docs.xibosignage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xibosignage.com/developer/contributing-to-xibo.md).
# Contributing to Xibo
The heart of the Xibo platform is open source software and always will be. If you benefit from Xibo and want to contribute to our project, you’re very welcome to do so. There are lots of different ways to be helpful no matter what your technical knowledge.
## Be active in the community
It sounds like a simple thing, but one of the most helpful things an experienced user of Xibo can do is be active in the community. Xibo is lucky enough to attract a huge variety of different users with different abilities, and the community is always busy with questions and requests for advice.
## Report bugs
If you’re sure something doesn’t work the way it should, or the way it's documented to work, then opening a topic in the [Get Help](https://community.xibo.org.uk/c/support/6) section of the Community forum with step by step instructions for reproducing the issue is super helpful. One of our support team can pick that up and pass it directly to the development team to be fixed in the next release.
## Suggest a feature or improvement
Xibo thrives on suggestions - much of the software does what it does because of our users describing how they want Xibo to work. If you have an idea for a new feature, or an improvement to something existing, open a topic in the [Feature Requests](https://community.xibo.org.uk/c/features/8) category of the Community forum.
A member of the support team will likely want to discuss that with you and find out a bit more (there is nothing worse than adding a feature which turns out to be not quite what you meant!), but once it's all understood they will pass it to the development team to be introduced in an appropriate release.
## Write some code
Xibo does not currently accept code contributions due in part to the recent wave of AI authored pull requests, but also to maintain the integrity and security of the product.
There are lots of ways you can integrate and extend Xibo without contributing to the core code, and these are discussed here.
## CLA
So that we can be confident in the future of the project, any contribution requires a CLA (contributor licence agreement) to be reviewed and signed [here](https://github.com/xibosignage/xibo/blob/master/CONTRIBUTING.md).
All development is on GitHub in the [xibosignage](https://github.com/xibosignage) organization. Xibo contains multiple components which are organised into their own repositories, we also have a central repository for collecting issues. This can be found [here](https://github.com/xibosignage/xibo).
## Release Cycle
Xibo actively works on two releases at any one time - the stable release and the development release. The stable release is in the `master` branch, and the development release is in the `develop` branch. It is always best to ask the best place to put your code before you start, as sometimes there can be framework changes between major releases.
You’ve refused my contribution!
We are always very sorry when your idea or contribution doesn’t fit with the project. There are lots of things we have to take into consideration before including something. Xibo has a lot of existing users we need to consider. We don’t want to be strict gatekeepers, but if we weren’t then you might find yourself a “victim” of a change that didn’t fit well.
Don’t worry though, you can still have your feature in your Xibo! We have built Xibo with an extensive set of tools to extend with custom additions and modifications. Xibo also has a comprehensive API.
Find out more in our [developer documentation](https://xibo.org.uk/docs/developer/).
---
# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.xibosignage.com/developer/contributing-to-xibo.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.