# Contributing guidelines
URL: https://docs.awellhealth.com/docs/extensions/contributing-guidelines

> For the complete documentation index, see [llms.txt](https://docs.awellhealth.com/llms.txt).



Awell's extensions are developed in the open. Contributions to the public `awell-extensions` repository
range from a question to a whole new extension.

> This page is the contribution path referenced from the `awell-extensions` repository README, so it's
> the canonical version. The repository points here.

## Discussions, issues, and new extensions [#discussions-issues-and-new-extensions]

### Discussions [#discussions]

Use discussions for questions, ideas, and anything that isn't yet a concrete change.

### Issues [#issues]

Use issues for bugs and specific, actionable requests. Include the expected behavior, what happened
instead, and how to reproduce it.

### Create an extension [#create-an-extension]

A new public extension is the most substantial contribution. See
[Build your own extension](/docs/extensions/get-started) and
[Create an extension](/docs/extensions/create-an-extension).

## What to expect from review [#what-to-expect-from-review]

### Smaller pull requests move faster [#smaller-pull-requests-move-faster]

Split a large change into focused pull requests wherever the work can be separated.

### Review is about reliability [#review-is-about-reliability]

Expect review comments and iteration. A public extension ends up in other people's care flows, so review
is about whether it holds up rather than how it's written.

## Coding style follows the repository [#coding-style-follows-the-repository]

Follow the conventions already in the repository. Extensions are TypeScript, and consistency with
surrounding code matters more than personal preference.

## License [#license]

Contributions are made under the repository's license.

## Next steps [#next-steps]

Back to [Extensions](/docs/extensions).