| name | comment-system |
| description | Use when implementing user comments and discussion threads. |
| metadata | {"id":"comment-system","category":"social","pattern":"Comment System","source":"uxpatterns.dev","url":"https://uxpatterns.dev/patterns/social/comment-system","sourcePath":"apps/web/content/patterns/social/comment-system.mdx"} |
Comment System
User comments and discussion threads
What it solves
A Comment System pattern helps teams create a reliable way to support threaded discussion around content while keeping moderation, authorship, and recovery visible. It is most useful when teams need article and discussion comments.
Compared with adjacent patterns, this pattern should reduce friction without hiding the state, rules, or recovery paths people need to keep moving.
When to use
- Article and discussion comments
- Team review threads
- Support and community conversations
When to avoid
- Avoid social or engagement mechanics when they do not create real user value.
- Do not add public counts or visibility states without understanding the trust implications.
- Do not ship the surface without moderation, abuse, or reversal planning.
Implementation workflow
- Confirm the pattern matches the problem and constraints before copying the example.
- Start from the anatomy and examples in
references/pattern.md, then choose the smallest viable variation.
- Apply accessibility, performance, and interaction guardrails before layering visual polish.
- Use the testing guidance to verify behavior across keyboard, screen reader, responsive, and failure scenarios.
