Our community has been granted early access to Threading / Inline replies. Yay! I have feedback on it - at least, on how it looks in my community. Not sure how much is skin-specific vs general.
I don't know where to send this feedback so I'm putting it here. Happy to move to a special Early Access group, if one exists, or email to the appropriate person & delete from here if needed.
One bit of meta-feedback about the Early Access process... I had to go back and forth with support several times to even get this new feature functional. And I have no knowledge of who to give my feedback to or what is expected to be correct vs buggy in this early access version. So, not the best experience as an Early Access user.
But, I digress. Here are my initial impressions of the Threading / Inline reply feature. This is on our staging site, on a responsive community with a pretty lightweight skin.
(1) Lots of spacing oddities even on a very basic thread page (w/ just one reply). See screenshot
(2) Not sure if this reaction will be generally shared amongst my fellow community managers, but I am surprised and disappointed that the thread continues to indent after 1 level of indent. This feels very old-school. Seems that the new model (Facebook, Slack, WebEx Teams) is to create just one level deep of "sub-thread". Screenshot.
(3) Looks bad on mobile; see screenshot for specifics
All of my complaints notwithstanding, I'm thrilled that Khoros is working on this!
I hope this feedback is useful.
Good feedback about the design.
Have you got any threads on your Staging site that are really, really long?
We're finding on Workshop that the longer the thread, seemingly the longer the editor takes to pop when a user tries to perform an inline reply. Eg https://www.workshop.com.au/t5/Whole-of-House/Introduce-yourself-to-the-community/td-p/65/page/68
It would be interesting to hear about your experiences of performance.
Hi @JasonHill -
I just created a thread on staging that spans 3 pages of "load more", and the editor still loads fine. I wonder what the difference is between our sites! (or maybe my thread just isn't long enough; I got tired of copy-pasting random replies :-))
@CarolineS Thanks for the feedback! It looks to me that some of your community CSS is inducing the inconsistencies you are seeing.
Please see the below screenshot
Please see below Responsive screen:
Hope this information helps. Please post here if there is more feedback.
@SohilM - Thank you very much for taking the time to look into the issues I reported, and giving detailed feedback. I really appreciate it!
It's too bad that we will need to enlist a developer to make this feature work for us; we don't have dev resources or budget so this will keep us from adopting the feature as soon as we'd like to. But such is life. (If you'd like to help us out with a PS engagement, we would happily take you up on it :-))
An additional piece of feedback after playing with the feature a bit - the reply editor textbox seems a bit short, vertically. Many of the conversations in our community have very long posts, and this short textbox isn't conducive to that. Is the height of the editor configurable?
Oh, and I'm glad that the # of threading levels is configurable! It would be great if that was documented in the release notes (apologies if it is and I missed it).
Once this looks good enough to share with our VIP community members, I'll have them try it out and give us feedback on the # of levels that seems most appropriate. My guess is just 2 levels, but we'll see!
The editor can be dragged vertically to increase the size of the text area. There is no configuration to specify a size.
Threaded levels configuration is not documented in the Release Notes. Will add the info in Release Notes.