The documentation of VerifHeep is fully in the docs. However, most of it is related to the specifics of the code, so it would be better to keep it as comments in the code instead and only leave in the docs the high-level overview.
Contributor guide
Research direction
Read the current VerifHeep documentation and the source code, then move the code specific details from the docs into comments within the code file.
Tech stack
python
Domain
documentation
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90
Daily Newsletter
Get fresh easy issues in your inbox.
Subscribe to GoodFirstIssue Daily for newly found easy issues that are ready for beginner-friendly open source work.
