openedx / openedx/docs.openedx.org
Create Dev Guide > Kotlin style guide
Open
Nobody has claimed this yet.
developers
- Dominant language
- JavaScript
- Stars
- 35
- Forks
- 95
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 3
Description
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 by reviewing the existing style-guide section at the linked documentation URL and determine how a Kotlin guide should fit there. The issue does not specify the guide's contents or source standards, so confirm its scope and acceptance criteria before drafting it. Done means a completed Kotlin style guide is placed in that section.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100