TeamAmaze / TeamAmaze/AmazeFileManager
Create a user manual for Amaze
Open
Nobody has claimed this yet.
Area-UIUX
Issue-Discussion
Issue-Task (low)
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
Much opensource software has a manual on their features, we can do a similar thing, starting with simple stuff.
References:
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
No files, tests, or entry points are named. Review the linked Blender, GIMP, and Krita manuals for structure, then inventory Amaze's simple features and define which user-facing workflows the manual should cover. Done means a published manual with agreed coverage and usable instructions.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100