First off, thanks for taking the time to contribute! Hypha is improved by a small community of developers, designers and users. We welcome your contributions. There are many ways to contribute to Hypha - code, design, documentation and translation.
Before you start working however, please read and follow this short guide.

Project meetings

Hypha maintainer's calls occur weekly. Meeting notes are available on our discourse forum.

Code of Conduct

We ask that follow our code of conduct.

Reporting issues

All changes in Hypha start as an issue.
Pick the correct issue template from the options given (bug report, feature request etc.). These templates will guide you. Provide as much information as possible.

Creating Pull Requests (PR)

Found a bug and know how to fix it? Have some design wireframes to improve some usability issues? Traslated Hypha into another language? Built a new feature you want to add? Great! Please read on.
  • Each pull request need to be linked to an issue. If non exist, create one first.
  • Rebase your topic branch on top of the main branch before creating the pull request.
  • One feature or fix per pull request.
You can find more detailed informatin on how to create a PR in the submitting changes page.

Ways to contribute


Code contribution

You probably want to read the documentation in the following order:
  1. 1.
    The system principles behind Hypha.
  2. 3.
    Choose one of the followng to get Hypha set-up in your local environment:

Documentation contribution

We use the hypha-docs Github repository, Gitbook to create and manage this website.

Design contribution

All design contributions are managed in Github issues. If you have a usability, or UX design recommendation, you can open a Github issue and use the "Status: Needs UX/UI Review" label.


Last modified 1mo ago