nextcloud / nextcloud/richdocuments
Mention the smart picker
Open
Nobody has claimed this yet.
1. to develop
pending documentation
- Dominant language
- JavaScript
- Stars
- 453
- Forks
- 147
- Avg merge
- 14h 54m
- Merged PRs (30d)
- 83
Description
What do you think about mentioning the smart picker in richdocument's README? Or is there any other more relevant place for that?
The goal would be to make it obvious to the admins and users that it can be used in NC Office.
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 reviewing the richdocument README and the existing documentation structure to determine where the smart picker is most relevant. Done means the chosen documentation location clearly tells Nextcloud Office administrators and users that the smart picker can be used there.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100