nextcloud / nextcloud/documentation
Email chapter needs a refactor
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 628
- Forks
- 2.5k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 135
Description
The Email (outgoing SMTP/etc) chapter is pretty confusing. It could use some reorganizing and editing, to cut down on support requests, bug reports, etc.
https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/email_configuration.html
Additional topic ideas too (WIP):
- Why to use an ESP (e.g. Mailgun) rather than Gmail [note: low volume accounts are still generally free]
- Oauth2 matters
- Conflicts between configuring in the Web UI versus via config file
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 with the linked Email configuration page and review its current organization and wording. Use the listed topic ideas to guide the reorganization, including ESP guidance, OAuth2, and conflicts between Web UI and config-file settings. Done means the chapter is clearer, more complete on these topics, and easier for administrators to follow.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100