Repository files navigation

Known bugs and intended new features are tracked usingGitHub issues. If you'd like to start working on an existing issue, comment on the issue that you plan to work on it so other contributors know it's being handled and can offer help. Once you have completed your work on this issue,submit a pull request (PR) to the p5.js main branch. In the description field of the PR, include "resolves #XXXX" tagging the issue you are fixing. If the PR addresses the issue but doesn't completely resolve it (ie the issue should remain open after your PR is merged), write "addresses #XXXX".

If you discover a bug or have an idea for a new feature you'd like to add, begin by submitting an issue. Please do not simply submit a pull request containing the fix or new feature without making an issue first, we will probably not be able to accept it. Once you have gotten some feedback on the issue and a go ahead to address it, you can follow the process above to add the fix or feature.

If you are here to edit or translate content, please do so insidethesrc/content/ folder.

For making code changes, please check out thetechnical overview to get started.

Follow the steps in theContributing Libraries doc if you would like to add your library to the collection!

We recognize all types of contributions. This project follows theall-contributors specification. Add yourself to thep5.js repository readme by following theinstructions here!

If you've contributed to this website (or any other part of the p5.js project), add yourselfhere. Instructions to do this can be found at the bottom of the section.