logisim-evolution / logisim-evolution/logisim-evolution
Documentation
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 7.6k
- Forks
- 1k
- Avg merge
- 17h 46m
- Merged PRs (30d)
- 68
Description
Hmmm, I also have to blame myself, but the current help system is out of date and needs some handling. Maybe a first step could be to first attack on the English version and than go to the other languages. Many new features are not/partly documented and make the use of logisim a lot easier to the targeted public, when documented. It would be great if we could maintain Carl Burch's standard of documentation; who wants to help?
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 locating the current English help system and comparing it with the newer features mentioned in the issue. The initial scope should be a clearly defined English documentation update; done means that selected features are documented consistently with Carl Burch's standard before work expands to other languages.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100