Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need for a prominent help or wiki page for provider settings #149

Closed
csb0730 opened this issue Mar 24, 2019 · 7 comments
Closed

Need for a prominent help or wiki page for provider settings #149

csb0730 opened this issue Mar 24, 2019 · 7 comments
Projects

Comments

@csb0730
Copy link
Contributor

csb0730 commented Mar 24, 2019

Experience with new users first installation of DC with various providers shows most of time problems with provider settings.

  1. currently it's hard to find a detailed description how to set up known problematic provider's settings.
  2. current descriptons at support forum partly seems to be wrong or outdated.

For new users it's hard to find provider settings at current web site. So without assistance of experienced used of DC it's impossible for a standard user to commission DC to a working state. Most of new users will throw away DC if they will run into this issue.

A prominent provider wiki or help is needed.

@csb0730
Copy link
Contributor Author

csb0730 commented Mar 24, 2019

Current solution by support forum is not a good solution!

@hpk42
Copy link
Contributor

hpk42 commented Mar 24, 2019

I mostly agree -- i think it could be its own little project to organize feedback and show useful hints about providers. Neither the support forum nor github appear to be good places for this. Then again, maybe having a github repo with one-page-per-provider and a web form/page that allows submitting "solutions" or "bugs" for getting setup with a particular provider, could do the trick. I guess a submission should typically translate into a PR. Not sure it makes sense to directly think about localization. Starting with text files that are rendered onto the delta.chat page, and only allowing PRs would be a start, the submission form could come later. We could also tell people to submit info to the support forum and then see to have people who transfer it to the provider overview. This "curation" step has the advantage that the information is probably presented more consistently.

@csb0730
Copy link
Contributor Author

csb0730 commented Mar 27, 2019

@hpk42 - Yes, It should be an own little project, so that everyone is aware of some issues with special providers. And that people see the requirement and have an easy single point of information where to address feedback from issues seen.

IMHO, a second possibility could be to add some provider related files to DC sources which are to be shown as prominent help in case of configuration errors while first DC setup:

For example:

  • provider.t-online.de.txt
  • provider.outlook.de.txt
  • provider.outlook.com.txt
  • provider.yahoo.net.txt

File should describe every step necessary to get provider working in detail and/or known issues which cannot be solved! (no autocrypt header transport for example).

@hpk42
Copy link
Contributor

hpk42 commented Mar 27, 2019

ok, all fine. At this point it's about someone starting this little project, not acquiring more requirements/wishes i guess ;)

@Simon-Laux
Copy link
Member

Simon-Laux commented May 24, 2019

I started a dedicated provider overview page https://github.com/deltachat/provider-overview.
Though it's not done and has no preview yet.

It currently looks like this:
provider

@lefherz lefherz added this to To do in Onboarding via automation Nov 24, 2019
@lefherz lefherz moved this from To do to In progress in Onboarding Nov 24, 2019
@endbacher
Copy link
Contributor

endbacher commented Dec 21, 2019

@csb0730 @Simon-Laux I agree with the initial post, for the time being I'd like to propose to

Not sure how / who can update the main web page (update: created an update and launched pull request but no idea if this is the correct/desired procedure), at least I didn't want to add anything to the German translation (finished now by the way but someone with some more detailed insight into the legal stuff should look into https://delta.chat/de/gdpr once update with translation becomes available to avoid any issues related to wording).

IMHO if we don't want to have the app only used by techies the setup and information should be as clear as possible for the average user.

@lefherz
Copy link
Contributor

lefherz commented Jan 20, 2020

  • The provider page is now linked at both get.delta.chat and the FAQ.
  • There is a separate project for this.
  • The information on how to configure problematic providers is currently integrated into the app: https://github.com/orgs/deltachat/projects/21

Thanks everyone :)

@lefherz lefherz closed this as completed Jan 20, 2020
Onboarding automation moved this from In progress to Done Jan 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Onboarding
  
Done
Development

No branches or pull requests

5 participants