[Docs] Improve clarity and consistency of comment notification behavior in Kanvas documentation

[Bhumikagarggg]

Current State

While testing and validating the comment notification system in Kanvas, I reviewed the documentation against actual observed behavior. Most scenarios are well documented; however, a few areas could benefit from clarification and alignment.

Observations

1. Owner Notification Behavior Not Clearly Defined

• Documentation states that design owners receive notifications for all comments
• However, it does not explicitly clarify that:
  Owners continue to receive notifications even when muting is applied
• This creates ambiguity with the general expectation that muting suppresses notifications

2. Inconsistency with Muting Behavior

• Docs mention that muted users do not receive notifications
• In practice:

1. Non-owners → muting works as expected
2. Owners → continue to receive notifications

• This distinction is not clearly documented

3. Missing Notification Hierarchy Explanation

• The relationship between:

1. Global preferences (Cloud settings)
2. Thread-level muting

• is not clearly structured
• A clear hierarchy (e.g., Global > Thread) would improve understanding

4. Tagging Behavior Could Be Better Structured

• Documentation mentions that tagged users do not receive notifications if muted
• However, behavior across:

1. thread-level mute
2. global preferences
3. owner role

• could be clarified with structured examples

---

Contributor Guide and Resources

• 📚 Instructions for contributing to documentation
  • Layer5 documentation site and source
• 🎨 Wireframes and designs for Layer5 site in Figma (open invite)
• 🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack