openedx / openedx/docs.openedx.org
Create a list of needed how-tos for Developers
Open
Nobody has claimed this yet.
developers
- Dominant language
- JavaScript
- Stars
- 35
- Forks
- 95
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 3
Description
What are the most important “how tos” needed for Developers? Goal to create a canonical list/outline that can be populated later (David Joy - overlap with backend and front end dev quickstart)
- Start a shared Sheets with interested contributors to begin collecting article title ideas
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start from the issue description and its proposed shared Sheets, while checking the noted overlap with the backend and front-end developer quickstarts. Done means producing a canonical list or outline of needed developer how-to article titles that contributors can populate later.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100