Welcome to the official documentation repository for the LIMO Cobot Developer Guide! Our aim is to provide a comprehensive and understandable guide to help developers program and control the LIMO Cobot using various programming languages and development environments.
Before you begin, please make sure you are familiar with basic Git operations and Markdown syntax. This will help you contribute and retrieve information more efficiently.
If you encounter any problems while using the guide or developing with the LIMO Cobot, please follow these steps:
- Visit the Issues page.
- Click the “New Issue” button to create a new issue.
- Provide as much detail as possible, including but not limited to:
- Description of the issue
- Steps to reproduce
- Expected vs. actual results
- Screenshots or code snippets, if possible.
- After submitting, please be patient for our team to respond.
We warmly welcome and encourage community members to improve documentation or add new content. If you wish to contribute, please follow these steps:
- Fork this repository to your GitHub account.
- Clone your forked repository to your local machine.
- Create a new branch for your changes.
- After making your changes, commit them to your fork.
- On GitHub, submit a merge request (MR) to the original repository’s
gitbook-en
branch. - In your MR description, clearly describe the changes you've made and why.
- After submitting your MR, please be patient for our team to review it.
We aim to maintain an open and welcoming environment, allowing everyone to contribute comfortably. Since we currently do not have a Code of Conduct, we ask you to simply be professional and respectful in your interactions within the project.
We recommend adding a Code of Conduct to your project to foster a positive and inclusive environment. GitHub offers templates such as the Contributor Covenant, widely adopted across open-source projects. You can create a CODE_OF_CONDUCT.md
in your repository and reference it here once added.
If you need any help, or have suggestions or feedback, please do not hesitate to contact us.
Thank you for your support and contributions!