# Guidelines for Contribution ## Why contribute? When we improve the base eVOLVER, all of the projects that are built on eVOLVER benefit from increased ease of use, reliability, and understandability. eVOLVER is too big for any one person to support. Currently, there is no dedicated staff to fix problems or be technical support. Therefore, we rely on our community of experts to improve the eVOLVER system. ## How can I help? Thank you for your interest in contributing to eVOLVER! **Even if you don't write code, you can still contribute.** We are always looking for assistance with creating or [updating documentation](/evolver/contributing/documentation.md) and [reporting bugs](/evolver/contributing/reporting-a-bug-hardware-failure.md). Ideas for **new features** are always welcome over at the [forum](https://www.evolver.bio/). Just make sure to search for your feature before posting. Please also consider developing the feature yourself! **Developers** are very very much appreciated! Follow the [software](/evolver/contributing/software-development.md) and [hardware](/evolver/contributing/hardware-development.md) development guidelines and post on the [forums ](/evolver/contributing/documentation/making-a-forum-post.md)if you get stuck. --- # Agent Instructions: 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: ``` GET https://khalil-lab.gitbook.io/evolver/contributing/guidelines-for-contribution.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.