-
All questions answered by Two.js maintainers are in the Issues section of the project with the label question. Ensure the question was not already asked by checking there first.
-
If you're unable to find a question that has been answered, create one. Be sure to include a title and clear description, as much relevant information as possible, and a code sample in situ or on a third party site like CodePen, jsfiddle, or glitch. This helps us to better help you.
-
Ensure the bug was not already reported by searching on the project under Issues.
-
If you're unable to find an open issue, open a new one. Be sure to include a title and clear description, as much relevant information as possible, and a code sample in situ or on a third party site like CodePen, jsfiddle, or glitch demonstrating the issue.
-
Open a new GitHub pull request with the patch.
-
Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.
- This is still in its infancy and if you're interested to help out, please send an email to [email protected] with the subject "Two.js Documentation". In the body of your email please describe why or how you'd like to help.
Two.js is a volunteer effort, so we apologize in advance for any delays.
Thanks! For both taking the time to read this and contributing.
Much ❤️ from the Two.js Team
This document is adapted from the Ruby on Rails project.