> For the complete documentation index, see [llms.txt](https://docs.omni-x.io/omni-x/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omni-x.io/omni-x/contribute/technical-contribution-guidelines.md).

# Technical Contribution Guidelines

The best way to contribute to Omni X is to fork, fix, commit and create a pull request describing your work in detail. No matter what repository, please follow the following structure to create a description for a pull request:<br>

**Title (mandatory) --** The title of the fix/feature\
**Description (mandatory) --** Describe what work have you done in as much detail as possible.\
**Related Issue (optional) --** If the pull request fixes an issue please tag the id of this issue.\
**Context (mandatory) --** Write down the context behind this feature/fix, what was the purpose of implementing it?\
**How has this been tested? (mandatory) --** Describe what testing you have done to make sure that the fix/feature works as intended and does not break the existing code.\
**Screenshots (mandatory) --** Please include a screenshot of your work. A frontend fix/feature should directly include a screenshot of your work. A backend fix/feature can include a screenshot of the hardhat output after running a test.&#x20;
