## On this page

Medplum is an open-source project, and we love both code and non-code contributions! People with any level of experience can make an important impact on the project: you don't need to be a professional developer! You might have just:

- **Ten minutes** to write a GitHub issue describing a bug you found or request for a feature you could use
- **One hour** to learn and participate in one of our webinars
- **Four hours** to author a case study showcasing how you've used Medplum

This section provides instructions on how to get started contributing to the Medplum project. If you're looking to _use_ Medplum, check out the [App](/content/docs/app/index.html) or [API](/content/docs/api/index.html) docs instead.

## Join our online community  
We have several online venues where Medplum community members and team members convene, offering various ways to get involved with the project:

1. Star the [Medplum Github repository](https://github.com/medplum/medplum)
2. Join our [Discord channel](https://discord.gg/medplum) \- and introduce yourself
3. Subscribe to [Medplum on LinkedIn](https://www.linkedin.com/company/medplum)
4. Follow [Medplum on Twitter](https://twitter.com/Medplum1)
5. Subscribe to our [Youtube channel](https://www.youtube.com/channel/UCu_sS6aXEHz3GPk2NTugtJA)

### Spread the word and participate  
Help us reach and engage people passionate about building amazing healthcare solutions!

1. Let us know your thoughts on [Github Discussions](https://github.com/medplum/medplum/discussions)
2. Share our [blog posts](/content/blog/index.html)
3. Share code, posts, videos or other content in relevant online forums for example [dev.to](https://dev.to/), [/r/healthIT](https://www.reddit.com/r/healthIT/), [/r/selfhosted](https://www.reddit.com/r/selfhosted/), or [Hacker News](https://news.ycombinator.com/)
4. Write content for your own blog or website, and [tell us about it](mailto:hello@medplum.com)

## Making a contribution  
There are several ways to make your first contribution to the Medplum project! The following instructions should help you get started.

### Reporting a bug or discussing a feature idea  
If you found a technical bug on Medplum or have ideas for features we should implement, the [GitHub issue tracker](https://github.com/medplum/medplum/issues) is the best place to share your ideas. [Open a new issue](https://github.com/medplum/medplum/issues/new) describing the changes you'd like to see, and one of our team members will respond.

### Writing documentation or blog content  
Did you learn how to do something using Medplum but it wasn't obvious on first try? Please contribute to our documentation!

Our documentation is hosted on [medplum.com/docs](/content/docs/index.html), but it is built from [Markdown](https://www.markdownguide.org/) files that live in our [Github repository](https://github.com/medplum/medplum/tree/main/packages/docs/docs).

For relatively small changes, you can edit files directly from your web browser on [github.dev](https://github.dev/medplum/medplum/blob/main/packages/docs/docs/home) without needing to clone the repository.

### Fixing a bug or implementing a new feature  
If you find a bug on Medplum and open a GitHub Pull Request that fixes it, we'll review it as soon as possible.

Before starting implementation of a new feature, open an issue first to discuss your plans and to ensure it fits into our roadmap and plans for the app.

If you're not yet an established contributor, your pull request needs to be linked to an issue labeled `open-to-community` (for example with a "Fixes #123" or "Closes #123" reference, or via the GitHub "Development" panel) -- this shows we've explicitly invited a community PR for that work. A maintainer can add this label to an existing issue, including one you just opened, on request. Pull requests that aren't linked to a qualifying issue are closed automatically; just reopen it once it's linked, or open the issue first if one doesn't exist yet. Medplum team members and established community contributors aren't subject to this requirement.

**Ready to get started writing code?** First things first, you need to [clone the Medplum repository](/content/docs/contributing/local-dev-setup/index.html).

Legal Note

By submitting content to this project, you agree to adopt the [Developer Certificate of Origin (DCO)](https://developercertificate.org/) for your contributions.

All conversations and communities on Medplum are expected to follow GitHub's [Community Guidelines](https://help.github.com/en/github/site-policy/github-community-guidelines) and [Acceptable Use Policies](https://help.github.com/en/github/site-policy/github-acceptable-use-policies).