Bug fixes and contributions are welcome!
If you're looking for ideas for where to get started, consider jumping in on any of these areas:
To contribute examples, please follow the current style of the examples. Add your example's title and file name to examples/js/ExampleList.json for it to appear in the examples list on the index page.
There is always more work that can be done on documentation. Especially adding good examples to methods and members to make the docs more informative and useful for people coming from diverse musical and technical backgrounds.
All of the docs are written in TypeDoc-style comments in the source code. If you catch a mistake, please send a pull request.
Along with this, it'd be great to integrate more visuals and references in the docs to help illustrate concepts.
If you are someone who is familiar with Tone.js, consider jumping in on the forum to answer some questions.
I'd love to see more tutorials for newcomers to Tone.js to help them get up and running or solve a particular issue. If you make a tutorial, please send me a link.
Tone.js has an extensive test suite using Mocha and Chai.
Along with more unit tests, it'd also be great to have more tests which run in the online context and generate music to help find bugs by ear that the automated tests might not illuminate. Audiokit, for example, has a great suite of aural tests.
You can also take a look at Tone.js' code coverage to get an idea of where more tests might be helpful.
If you'd like to contribute a cool and expressive synth or effect, I'd love to hear it. Please send me an example that I can play with along with the PR.