This plugin is inspired by Pavilion’s fantastic work on the Question Answer Plugin. As always, thank you for your continued contributions to the Discourse project.
I am a bit of a Q&A fanatic, so I’m excited to see this new post format available in Discourse and tickled by how… familiar… it seems! I have some questions about the functionality and how customizable it is. Much of this may be answered in the plugin package but I figure it might be helpful to have here, too…
Is there education built in for the plugin that teaches users about the feature, how/when to use it, etc? I love @discobot - maybe there’s a tutorial/onboarding module for Q&A?
You say admins can set the default within a category to Q&A - if they do, are topics required to be Q&A or do they just default to it?
If it’s a default, is there an option to require it? Can Q&A be disabled by category, too?
If a category is set to default to Q&A, is this something that’s apparent to users? I see that the post creation button will say it’s a Q&A but I can imagine a seasoned user’s first interaction with the newly-added feature might lead them to overlook the text without something drawing attention to the post type before it’s submitted.
Has anyone been able to limit the amount of votes per user per topic? In our case, we are running photocontests, and we would like to limit each user to 5 votes max per topic.
in this post I was directed to post the issue here to give the feedback.
In the thread linked above in the OpenStreetMap forum, where this plugin is used in some categories, user interface shortcomings with this plugin are discussed.
In short there are:
This plugin forbids to post a reply to a reply. It is debateable if this should be enforced or to be configurable on a per-instance basis, but it it is enabled, the following occurs:
The user can select some text and quote. The user can enter a reply. Only at the very end, when the reply is to be sent, it is aborted with an error message
An error occurred: You are not allowed to create a post in reply to another post.
This is a not really helpful message. It does not tell what is wrong. In fact, if a reply is not allowed, it should not have allowed “quote-reply” in the first place at all.
When a reply is sent via email, the email just vanishes without the sender beeing informed. There should be a bounce with an explanatory message saying what is wrong.
Only comments are allowed. But they swallow some formatting (e.g. quotes, see the comment on this post), and also they are limited in numbers of characters, prohibiting more complex thoughts.
Went searching for this same thing and was surprised it hadn’t been brought up before. Allowing the user to always end up in an error state with quotes and no option for markup in comments offers a very disjointed experience. Additionally, the error messaging is unclear for users when trying to directly reply to a post.
Definitely hoping to see an improvement to help polish this UX.
this post