You'll have noticed that there is a very common stone-and-sand pattern: person A writes something, and people B, C, and D discuss it. Such a common pattern, but still hard to use when the discussion gets long.
In my experience, the two main ways we navigate a long discussion are:
- To jump straight to the reply to one of our comments, using the link in the notification email
- To read the latest comments
And reading the latest comments is always a pain. It requires scrolling down to the end of the page, or on forums that use pagination, clicking "Last page" and then scrolling down to the end of that page.
Some non-Wikidot forums use collapsible comments, with various tricks to rank comments from "flamebait" to "interesting" but that makes the whole user interface more complex again. I like the idea of collapsible comments but it should really collapse everything we've already read, and leave visible the stuff we've not yet seen. That is just hard to do, technically (the caching we use for speed means most page views are not user dependent).
So, a simple experiment: reverse comment order. I'm using this on the blog now, which I did by editing the blog:_template page so that it says: [[module Comments order="reverse"]]. That's a new feature in the Comments module we pushed out today. Comments show in reverse order, though replies to a comment show below it, as you'd expect. To make this obvious to the reader, the 'add a new post' box is at the top of the page, rather than the bottom.
Try this, here and on your sites, tell me what you think.
Thanks to teh developer team for the implementation!
I hope, this iwll work on nested comments too… :) W will see.
Service is my success. My webtips:www.blender.org (Open source), Wikidot-Handbook.
Sie können fragen und mitwirken in der deutschsprachigen » User-Gemeinschaft für WikidotNutzer oder
im deutschen » Wikidot Handbuch ?
Seems to work nicely when one replies properly to a comment rather than posting a new comment. Some threads look a little strange, especially where people have replied by creating a new post rather than 'reply'.
Portfolio
I'm of the opinion that it would be better to remove nesting completely - and make use of quoting instead.
It's a lot easier to understand, and the post that is being replied to is still right next to the actual reply (albeit, it's in a quote-box instead of a separate post, but you know what I mean)
I really dislike the whole nesting thing ;) Is there any possibility that it might be removed in future, possibly even as an optional parameter to the Comments module?
~ Leiger - Wikidot Community Admin - Volunteer
Wikidot: Official Documentation | Wikidot Discord server | NEW: Wikiroo, backup tool (in development)
you can remove it.
admin:manage
forums
discussion
set it to "0" flat/linear
Nesting does indeed add complexity especially with reverse comment order. My replies somehow don't appear where they should. I'm going to change the blog comments to work with a flat linear structure, to see if this works better.
We may also try to show the comments totally reversed, rather than just the posts but not the replies.
Portfolio
Well, tried that, but the nesting still shows, and the Reply actions disappear.
I see another issue with nested comments, namely the comment count is wrong. It counts comments at the top level but not replies.
Portfolio
This is a direct solution to my wish in the community: #58!
Thankyou SO MUCH!
I noticed that by reversing the order, the comment form appears on the top… it would be nice if we could choose whether the comment form goes on the top or on the bottom — regardless of the order selected.
Personally, I'd prefer the form at the top with the oldest-newest ordering, or the form at the bottom with the newest-oldest ordering ;D
James, I'm trying to avoid configuration and make things work "as they should". Since you conceptually add new comments at the top or the bottom of the page, that's where the new comment box goes in this design.
I'm thinking however that it's still a pain in oldest-newest ordering to scroll to the bottom to enter a comment. When we've made the simplified comment user interface, we just put comment boxes at both ends, once we get more than 10 comments or so.
Portfolio
A good compromise!
Oh yes! Thanks so much! Comments are now a lot easier to navigate and read!
Timothy Foster - @tfAuroratide
Auroratide.com - Go here if you're nerdy like me
With order="reverse" the comments are going in both ways:
Makes reading a full thread more challenging than if it were not reversed.
This flexibility is good. It's flexibility that should be in the hands of the reader.
Why not provide a default set by the admin / thread-creator, and options for sorting available to the reader.
"branched", "sort newest", "sort oldest".
I fully agree.
I have the same opinion for themes… but it's off topic. :-)
Order by number of comments would also be handy!
A - S I M P L E - P L A N by ARTiZEN a startingpoint for simple wikidot solutions.
Are you referring to the ListPages module? If so, I can't think of any situations I'd use that but would still like to see it added :)
~ Leiger - Wikidot Community Admin - Volunteer
Wikidot: Official Documentation | Wikidot Discord server | NEW: Wikiroo, backup tool (in development)
take a look at http://ethischforum.wikidot.com/begrip:behoefte0 at the right hand side you can see a column commentaar. This is a list of al the comments given on the site… but with comment on page… not in a forum… I wish to see the comment with the most action at the top of this list…
A - S I M P L E - P L A N by ARTiZEN a startingpoint for simple wikidot solutions.
@Steven_Heyndrickx: yes, I agree. "Top threads" is important and should work when we make forums with ListPages.
Portfolio
I much prefer linear threaded comments with quoting. It's much easier to read and the flow of the thread is usually more consistent or at least, if the topic wanders, it's easier to follow.
The Chronicles of Heaven's Gate
A 4th edition Dungeons & Dragons campaign setting.