Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.
Please ensure your pull request adheres to the following guidelines:
- Search previous suggestions before making a new one, as yours may be a duplicate.
- Make sure the new resource is useful before submitting. That implies it has enough content and every item has a good succinct description.
- Make an individual pull request for each suggestion.
- Use title-casing (AP style).
- Use the following format:
[Resource Title](link) - Resource short Description (2 lines or less in total).
- Link additions should be added to the bottom of the relevant category.
- New categories or improvements to the existing categorization are welcome.
- Check your spelling and grammar.
- Use the correct spelling and capitalisation for
BBC micro:bit
,micro:bit
, andMicro:bit Educational Foundation
(resource title could be excluded if there is a good reason). - The pull request and commit should have a useful title.
- The content linked is in English or contains an English translation.
Thank you for your suggestions!
If you have something awesome to contribute to an awesome list, this is how you do it.
You'll need a GitHub account!
- Access the awesome list's GitHub page: https://github.com/carlosperate/awesome-microbit
- Click on the
readme.md
file: - Now click on the edit icon.
- You can start editing the text of the file in the in-browser editor. Make sure you follow guidelines above. You can use GitHub Flavored Markdown.
- Say why you're proposing the changes, and then click on "Propose file change".
- Submit the pull request!
Sometimes, a maintainer of an awesome list will ask you to edit your Pull Request before it is included. This is normally due to spelling errors or because your PR didn't match the awesome-* list guidelines.
Here is a write up on how to change a Pull Request, and the different ways you can do that.