openedx / openedx/docs.openedx.org
Dev Guide > XSS material
Open
Nobody has claimed this yet.
developers
- Dominant language
- JavaScript
- Stars
- 35
- Forks
- 95
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 3
Description
https://docs.openedx.org/en/latest/developers/references/legacy_guide/preventing_xss/index.html
Break up 9.1 into smaller sections:
- One doc on Concepts: what and why
- One reference for each type of code (9.1.3 should be broken down, and all Mako & Underscore template should be under one page called “Legacy Templates”)
- 9.2 “sanitizing input” should be converted to a simple reference doc
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 with the linked preventing XSS guide, especially sections 9.1, 9.1.3, and 9.2. Review how the current material is organized, then split it into a concepts document, references for each code type, a Legacy Templates page for Mako and Underscore templates, and a simple sanitizing-input reference. Done means all listed sections are reorganized into those documents.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100