You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: contributing.md
+5-2
Original file line number
Diff line number
Diff line change
@@ -13,14 +13,17 @@ Please note that this project is released with a [Contributor Code of Conduct](c
13
13
Please ensure your pull request adheres to the following guidelines:
14
14
15
15
- Search previous suggestions before making a new one, as yours may be a duplicate.
16
-
- Make sure the list is useful before submitting. That implies it has enough content and every item has a good succinct description.
16
+
- Make sure the new resource is useful before submitting. That implies it has enough content and every item has a good succinct description.
17
17
- Make an individual pull request for each suggestion.
18
18
- Use [title-casing](http://titlecapitalization.com) (AP style).
19
-
- Use the following format: `[List Name](link)`
19
+
- Use the following format: `[Resource Title](link) - Resource short Description (2 lines or less in total).`
20
20
- Link additions should be added to the bottom of the relevant category.
21
21
- New categories or improvements to the existing categorization are welcome.
22
22
- Check your spelling and grammar.
23
+
- Use the correct spelling and capitalisation for `BBC micro:bit`, `micro:bit`, and `Micro:bit Educational Foundation` (resource title could be excluded if there is a good reason).
23
24
- The pull request and commit should have a useful title.
25
+
- The content linked is in English or contains an English translation.
0 commit comments