nextcloud / nextcloud/richdocuments
Documentation cleanup
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
- Cleanup docs/
- Maybe move to documentation repo as we have nextcloud office sections there
- https://github.com/nextcloud/richdocuments/pull/3137
- https://github.com/nextcloud/richdocuments/pull/3141
- Check for missing app config flags
-
occ config:app:set richdocuments uiDefaults-UIMode --value="compact" -
occ config:app:set richdocuments theme --value="collabora"
-
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 docs/ and the two linked richdocuments pull requests to identify the documentation changes and any possible move to the documentation repository. Check the listed occ config commands and related app configuration for missing flags. Done means the documentation scope is resolved, relevant content is updated or relocated, and the configuration coverage is verified.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100