# Hardware Development

## Design Ethos

eVOLVER Hardware strives to be:

1. Modular
2. Extensible
3. Programmable
4. Robust
5. Affordable
6. Accessible (easily sourced parts, open source designs and information)

## Steps

1. Make an issue on the hardware [GitHub](https://github.com/FYNCH-BIO/hardware)
2. Characterize the problem on the [forum](/evolver/contributing/documentation/making-a-forum-post.md)
3. Make changes and add to your forum post
4. Make a pull request on [GitHub](#hardware-github-contribution-guide)

## Hardware GitHub Contribution Guide

Once the new hardware has been tested by the community, follow the guide for contributing to GitHub as outlined on the [software page](/evolver/contributing/software-development.md).

CAD file contributions should be uploaded in the following formats:

1. .sldprt or .f3d - Solidworks or Fusion360 Archive files. These contain the design history of the part, making future editing much easier.&#x20;
2. .step or .stp files to support editing via any common CAD tool
3. .stl file for 3D printing and model viewing.


---

# 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/hardware-development.md?ask=<question>
```

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.
