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

# Contributing

Sylius grows through community work.

You can contribute code, documentation, translations, reviews, and feedback. Each contribution improves the product for everyone.

### What this section covers

This section helps you choose the right contribution path.

* [Contributing Code](/public/open-source/contributing/contributing-code.md) covers changes to the product itself.
* [Contributing Documentation](/public/open-source/contributing/contributing-documentation.md) covers improvements to guides, references, and examples.
* [Contributing Translations](/public/open-source/contributing/contributing-translations.md) covers language updates and localization work.
* [Key Contributors](/public/open-source/contributing/key-contributors.md) highlights the people helping shape the project.

If you plan to contribute code, start here:

* [Submitting a Patch](/public/open-source/contributing/contributing-code/submitting-a-patch.md) explains how to prepare and send a change.
* [Security Issues](/public/open-source/contributing/contributing-code/security-issues.md) explains how to report vulnerabilities safely.
* [Coding Standards](/public/open-source/contributing/contributing-code/coding-standards.md) defines the expected code style.
* [Conventions](/public/open-source/contributing/contributing-code/conventions.md) describes shared implementation patterns.
* [Sylius License and Trademark](/public/open-source/contributing/contributing-code/sylius-license-and-trademark.md) explains the legal boundaries for reuse and branding.

### Principal rules

Follow a few core rules before you open a contribution:

* Keep changes focused. One problem, one clear fix.
* Respect existing standards, conventions, and release policies.
* Prefer small, reviewable improvements over broad rewrites.
* Report security issues privately. Do not disclose them publicly first.
* Make every change reproducible, testable, and easy to understand.

### Spirit of open source

Open source is more than public code. It is shared ownership.

Contribute in a way that helps the next person build on your work. Write clearly. Explain intent. Leave context. Assume good faith during review.

Good open source work values maintainability over cleverness. It favors collaboration over ego. It treats feedback as part of the process, not a blocker to it.

The best contributions solve real problems, fit the project’s direction, and make life easier for users and maintainers.

### Where to start

Pick the contribution type that matches your goal.

* Fix behavior or add a feature — start with [Contributing Code](/public/open-source/contributing/contributing-code.md).
* Improve clarity or accuracy — start with [Contributing Documentation](/public/open-source/contributing/contributing-documentation.md).
* Improve localization — start with [Contributing Translations](/public/open-source/contributing/contributing-translations.md).


---

# 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.sylius.com/public/open-source/contributing.md?ask=<question>&goal=<endgoal>
```

`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.