The Code of Conduct applies to all contributions (PRs, issues, comments, etc). Thanks!
- Fork the project.
- It's up to you whether you'd like to work on your fork's master or a feature branch. The latter would probably be more useful if you're submitting an idea that has more in-depth guidelines.
- One idea = one commit, please. Write commit messages in the present imperative tense, so that they read as changes to be applied to the repo rather than a diary of changes made ("Add the widget" would be correct, vs. "Added the widget").
- Submit a PR to the master branch!
- Follow this style of Markdown. We're using asterisks instead of dashes for bulleted lists.
- If you add an idea to the list:
- Follow the same imperative grammatical structure: "Do a thing", instead of "A thing"
- If your idea has more in-depth guidelines than a simple sentence, format your idea in the list as
Do a thing ([Guidelines](docs/your-idea.md)). As shown in this example, the word "Guidelines" links to a markdown file in thedocs/folder detailing your project idea's guidelines.