I’m interested, would it be possible to move the post that is marked as “Solved” up to the top right after OP post, without touching the core of the Discourse? I mean with just tweaks within the plugin itself. I would appreciate if you could give me some hints how to achieve it.
I think it makes sense, for example when the post that solves the OP post it deep down. Users will not have to endlessly scroll to find it. There are SEO considerations too. I guess the post that is marked as Solved contains the most important and the most relevant information that we want to present to Google above all other content.
Changing ordering of the stream is something we actively avoid, its a complex change of dubious benefit. It can confuse users to read stuff out-of-order and is very technically tricky to pull off efficiently.
I previously suggested that the “X replies” field (& functionality) would be used on OP, since that’s a guaranteed free space and an interaction users are already trained on.
I think this makes it much easier for people who come across the topic later to find the useful information quickly, while also keeping it nice and simple for people who want to read the whole thread.
This functionality requires some changes to Discourse’s core to add “custom filters” to TopicView. I’ve based this on the recent additions of custom filters to TopicQuery, so I hope I have gone about it in the right way. The pull request to core is here: https://github.com/discourse/discourse/pull/4740
Ah well, maybe I misunderstood @erlend_sh’s post & screenshot above - I thought this was what he was suggesting, and what @codinghorror agreed with .
I get the argument for duplicating the answer rather than collapsing everything down. In the meantime I’ll stick what I’ve done in a separate plugin so I can use it in my community.
Aside from discourse-solved, I do think having functionality for custom filters on TopicView would be useful for plugins in future. Is adding that extensibility something you would consider?
One thing I’d like to do with it is create a plugin to make specific categories more useful as “knowledge-bases” - so you’d have the first post of every topic as a wiki post, and all other posts would be “hidden” unless the user particularly wanted to see the conversation.
So you’d end up with something like this, but without having to make the topics read-only/closed.
It also opens up the possibility of doing topic-summary type things using plugins, like what is described in this spec:
I would stick with the original request. Sorry, I saw the expansion arrow on @erlend_sh’s mockup and assumed it worked like a standard quote. But I think you are correct, Erlend had a different idea here, one that I don’t really agree with.
Again, let’s all practice with how it works on a regular quote… just click anywhere in the top bar (where it says “David Taylor”) to expand it:
That is how the accepted answer should expand on the first post. It is an implicit quote.
I kind of disagree you should even allow people to clutter your “howto” or “faq” or whatever topics with discussion, this is not the right place for it.
They should reply as linked topics and then you would have a list of stuff that links to it which is quite clean. Anyway better open another topic on knowledge base, it is a bit off topic here.
Should we display solved by david in post #2 in the header, or should it look like other quotes and just say david along with an avatar. If the latter, how do we indicate it is indeed the answer.
Currently, if you go and change the “solution” then it causes the page to jump around all over the place because the height of the first post is changing. This happens with the discourse-solved plugin right now, but it’s not really noticeable since it’s only 1 line of text. I’m not really sure of a solution for this… Either we don’t update it live (so you have to reload the topic to see the quote), or have some kind of placeholder when the topic isn’t solved.
A possible solution to point 2 could look like this:
Solved by david is perfect, make sure it has the down chevron affordance so people know it is expandable.
Only if the solution is currently expanded in the first post, right? I think that’s sufficiently enough of an edge condition that we can ignore it for now.
It’s reusing the quote UI from the rest of discourse, so clicking/tapping works anywhere along the bar, except of course on the links david and post #2
.
) sure is what is described above:
