OWASP / OWASP/OCSD

Curriculum Module Format Standardization

Open
#40 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
40
Forks
16
Avg merge
1d 1h
Merged PRs (30d)
5

Description

Looking at the existing content, I think it is necessary to define a well-structured template and set of requirements for each module to follow. This standardization would make modules easy to contribute to and evaluate for completeness.

@Shruti-s-kulkarni Does something like the following work?

Title / ID

Description and Scope

Key Concepts and Terminology

Core Content

Topic 1
Topic 2

...

Resources

References
Labs and Exercises

...

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the existing module content and compare its structure with the proposed Title/ID, Description and Scope, concepts, core content, and resources sections. Define the required template and completeness criteria, then document the agreed standard so contributors and evaluators can apply it consistently.

Written by the indexing model from the issue text.

Assessment

Domain
content, documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.