LemmyNet / LemmyNet/lemmy-docs
Add documentation page to explain the code structure
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 108
- Forks
- 95
- PR merge metrics
- No merged PRs in 30d
Description
Starting with an explanation what each subfolder in crates/ is for.
Contributor guide
No contributing guide indexed for this repository
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 subfolders in crates/ and the existing documentation structure. Document what each subfolder is for; done when the new page explains the purpose of all crates/ subfolders.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100