I’ve been working on some designs for the help page (yunohostDOTorg/#/help).
The easy part is the UI design - the more difficult part is the information architecture and creating a short and straight user journey for people looking for support.
Different users have different levels of “technical skill”. Some post to the yunohost forum, some to Github issues.
The ideal situation is all support bugs/issues/messages are unified, so if a message is updated on one channel, it’s updated on all.
Discourse have a plugin that allows discourse users to “bridge” communications between a discourse instance and Github.
I propose we test it to see if it allows unification messages in a specified Discourse category(ies) to specified Github repo issues.
This would allow users familiar with Github to post issues there, and they would be visible to Discourse users, and vice-versa.
Possible use case
I am a Yunohost user who has tried to install Yunohost.
I am familiar with basic sysadmin tasks - installing an OS on a machine, upgrading packages, removing packages, following configuration guides.
When I report issues/bugs, I’m not familiar with the defined structure an clear structure needed. Often my issues need some over-and-back between me and the more experienced people in the project.
I’ve come across a problem, and need help. I don’t have a Github account.
I want to post a message in the forum.
If this plugin allows Github issues and forum support issues to be unified it:
- Yunohost users can post in either GH or the forum and their message can be responded to in either
- the Yunohost contributors and maintainers have only one place to look at issues (which ever they like! )
- Yunohost users are not confused about “where do I post my message??”
- the YNH/help page gets simpler
Someone with forum admin rights install the plugin and see what is actually possible with it.
I’m happy to help, test configure things.