-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Issue Process
Issues that say help-wanted
are things we're encouraging members of the community to do. These are small, person-sized projects that will materially improve the curriculum.
In order to resolve an issue, fork the curriculum to your personal account. Make a branch off of master
. Name your branch according to what you're working on- for example add-mdn-links
or javascript-security-workout
. File a pull request, and then reference the issue you are working on with the number. Your branch does not need to fully resolve the issue, every little bit helps, but we might wait until someone else builds on your work before we merge it to master (if it's a workout for a course that isn't live, for example.)
There are labels according to Topic, so you can filter based on what you have expertise in. There are also labels according to the type of task, such as adding a community resource or exercise, covering an objective with new content, or reviewing sections of the curriculum that are being tagged by users as having problems.
Want to contribute to this wiki? Go right ahead! If it has to do with how the Enki software ecosystem works, or editorial guidelines for how to write, let us handle that. Anything else, edit away!
Curriculum Format:
- Topic Documentation
- Course Documentation
- Workout Documentation
- Insight Documentation
- Glossary Documentation
Contributor Resources:
Curriculum overview:
Topic pages: