Conversations on writings

When someone posts something, whether a research, documentation, a log or just a thought, then we must allow an easy way for others to review and discuss what was written
Shawn Mclean

Overview

This will serve as a decision and research document for determining the design choices when building the Writing Conversation system.

A writing is a piece of document that contains words, images and videos. It will eventually contain dynamic maps, diagrams and data reports.

Every piece of information should give users the ability to select/highlight and comment.

Questions

  1. Should we display the discussion at the bottom or to the side?

  2. Should we show the latest at the top or bottom?

  3. Should the comment input be at the top or bottom?

  4. How deep should replies go? Deep nest vs threads?

Should we display the discussion at the bottom or to the side?

References

Should we show the latest at the top or bottom?

References

https://ux.stackexchange.com/questions/37818/what-is-better-than-top-posting-and-bottom-posting

Should the comment input be at the top or bottom?

How deep should replies go? Deep nest vs threads?

Possibly follow the github discussion model?

Decision

ChatGPT research:

Deep nesting comment systems are used on various online platforms to organize and structure conversations. Like any system, they have their own set of advantages and disadvantages. Here are some pros and cons to consider:

Pros:

1. Clear hierarchy: Nested comments provide a clear visual hierarchy, making it easier to follow the flow of conversation, understand who is replying to whom, and distinguish between different discussion threads.

2. Encourages engagement: Since nested comments make it easier to reply to specific comments, they can foster more focused, relevant discussions, which can lead to higher engagement among users.

3. Easier moderation: Nested comments can make moderation easier, as moderators can more readily identify off-topic or inappropriate comments and remove them without disrupting the entire conversation.

4. Reduces redundancy: By allowing users to reply directly to specific comments, nested systems can help reduce redundant or repetitive content, as users are less likely to restate points already made by others.

5. Promotes continuity: Deep nesting can help maintain the continuity of conversations, as users can easily reference and build upon previous comments within the same thread.

Cons:

1. Readability issues: Deep nesting can sometimes lead to decreased readability, as comments may become progressively indented and compressed, making it difficult to read longer threads.

2. Overwhelming for users: A deeply nested comment system can be overwhelming for new users, who may find it challenging to navigate and participate in conversations.

3. Difficulty finding recent comments: In a deeply nested comment system, it can be difficult to locate the most recent or relevant comments, as they may be buried within a long thread.

4. Encourages tangents: While nested comments can foster focused discussions, they can also lead to lengthy, off-topic tangents that may detract from the main conversation.

5. Limited space: Depending on the platform's layout and design, deep nesting can lead to limited horizontal space for displaying comments, which can result in cramped or truncated text.

Ultimately, the effectiveness of a deep nesting comment system depends on the context in which it is used, as well as the platform's design and user base. Platforms should carefully consider their audience's needs and preferences when determining the best comment system to use.

Prompt: Pros and cons of deep nesting comment systems

References

https://docs.github.com/en/graphql/guides/using-the-graphql-api-for-discussions#objects