The AMP Project would not be possible without help from all members of the community whether you are a developer, content creator or provider of services relevant to AMP. There are many ways for you to contribute.

Reporting issues with AMP

If you have feedback or are experiencing technical issues with AMP, please file it using the issue tracker. If you're having issues with ampproject.org, please use the docs issue tracker instead.

Providing technical contributions to AMP

The AMP Project strongly encourages technical contributions!

We hope you'll become an ongoing participant in our open source community, but we also welcome one-off contributions for the issues you're particularly passionate about.

Helping with code

To get started with contributing code to the AMP Project read through the CONTRIBUTING file, which includes details of the process by which a feature or bug fix goes from concept to submission and how you can participate in technical designs and discussions.

When you're ready to work on some code, the DEVELOPING file has documentation of how to get the code and start developing.

If you want to help out but aren't sure where to get started, we have a list of starter issues that you can use to learn more about the AMP Project code and make an immediate impact.

Helping with documentation

Documentation is important for the entire AMP community, and we would appreciate your help in making our documentation better! We've got all sorts of documentation--examples for users of AMP, docs to help AMP Project contributors, etc.

ampproject.org is where most people get familiar with AMP. You can contribute to documentation in the ampproject docs GitHub project. (You can even make the page you are reading better!)

ampbyexample.com provides examples of how to use AMP. You can improve it at the amp-by-example GitHub project.

You can also help make things better for other contributors to the AMP Project by improving our documentation in the amphtml GitHub project.