> For the complete documentation index, see [llms.txt](https://developers.weglot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.weglot.com/cms/craft-cms/github-repository.md).

# GitHub repository

The plugin is open source — browse the code, report issues, and contribute.

The Weglot plugin for Craft CMS is developed in the open. Its full source code lives on GitHub at [weglot/translate-craftcms](https://github.com/weglot/translate-craftcms). You are welcome to read the code, report issues, suggest improvements, and contribute.

### Report an issue or request a feature

Open an issue on the [repository's issue tracker](https://github.com/weglot/translate-craftcms/issues). To help us reproduce a bug, please include:

* the steps to reproduce it,
* your Craft CMS and Weglot plugin versions,
* your PHP version,
* any relevant errors from your Craft logs.

{% hint style="info" %}
For account, billing or urgent matters, contact <support@weglot.com> rather than opening a public issue.
{% endhint %}

### Follow releases

Every release is documented in the [CHANGELOG](https://github.com/weglot/translate-craftcms/blob/master/CHANGELOG.md). Check it before upgrading to see what changed.

### Contribute

Pull requests are welcome:

1. Fork the repository and create a branch for your change.
2. Follow the project's coding standards (PSR-12 and the Craft CMS coding guidelines).
3. Run the quality suite and make sure everything passes.
4. Open a pull request describing your change.

```bash
composer run check-cs   # code style (dry-run)
composer run phpstan    # static analysis
composer run rector     # code modernization
composer run test       # unit tests
```


---

# 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://developers.weglot.com/cms/craft-cms/github-repository.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.
