# Contributing to KaiUI

#### **Did you find a bug?**

* **Ensure the bug was not already reported** by searching on GitHub under [Issues](https://github.com/AdrianMachado/KaiUI/issues).

* If you're unable to find an open issue addressing the problem, [open a new one](https://github.com/AdrianMachado/KaiUI/issues/new). Be sure to include a **title and clear description**, as much relevant information as possible, and a **code sample** or an **executable test case** demonstrating the expected behavior that is not occurring.

* If possible, use the relevant bug report templates to create the issue.

#### **Did you write a patch that fixes a bug?**

* Open a new GitHub pull request with the patch.

* Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.

* Inlcude screenshots or screen video captures for all UI related work, before and after behaviour

#### **Do you intend to add a new feature or change an existing one?**

* Suggest your change to [Adrian](https://github.com/AdrianMachado) and start writing code.

* Do not open an issue on GitHub until you have collected positive feedback about the change.

* Several feature issues that are currently open are most likely more high pri, so please prioritize them before suggesting new features

#### **Do you have questions about the source code?**

* Ask any question about how to use KaiUI to [Adrian](https://github.com/AdrianMachado).

Thanks! :heart: :heart: :heart:

KaiUI Team

__Credits to the Rails team for providing a template for this contributors guide__
