Reaction chips match the kit. Should the composer support @Cara style mentions?
Comment thread
Comment thread is a Rich Editor block from Orvain UI, built for React and Vue with a matching Figma frame.
Best for
Reviews and discussions where the reply matters most: read the thread, answer with full formatting
Anatomy
Header with title, count, people and ⋯ · comments with avatar, verified seal, presence, Author pill, role tag, time and mention chips · composer with a grey tray: B I U S, colour, lists, link, code, @ mentions, emoji, attach, Send · ⌘↵ hint and count
Design review
2 commentsThread options
Yes, and keep the full formatting: lists, links and inline code all work here.
Bold⌘B
Italic⌘I
Underline⌘U
Strikethrough⌘⇧X
Text color
Bulleted list⌘⇧8
Numbered list⌘⇧7
Link⌘K
Inline code⌘E
Mention@
Emoji
Attach file
In the Orvain Library
Get Comment thread for your product
The block’s code in React and Vue, its frame in the Figma file, and the Orvain MCP so your AI tools build with it. Part of every Library plan, alongside every other block.
- React
- Vue
- Figma frame
- Orvain MCP
About this block
Part of Rich Editor
What’s inside
04parts
The pieces it is built from. Keep them all, or drop the ones your product doesn’t need.
- Header with titlecount, people and ⋯
- Comments with avatarverified seal, presence, Author pill, role tag, time and mention chips
- Composer with a grey trayB I U S, colour, lists, link, code, @ mentions, emoji, attach, Send
- ⌘↵ hint and count
Responsive behaviour
560 px
Drawn at this width and never stretched past it. Below it, controls, text and spacing step down from the box the block sits in, not the window.
1440pxDesktop · 12 columns
When to use it
Where Rich Editor earns its place
Reach for Rich Editor
- Long-form content read as a page: documentation, articles, release notes.
- Replies where a quote or an @mention changes what the sentence means.
- Authors who will never learn markup and should not have to.
- A writing surface meant to stay clean until the writer selects something.
Reach for something else
- Text engineers will review in a diff. Markdown in a plain field stays readable in version control; rich output does not.
- A single line with no formatting, such as a title. Use a text input and keep its validation, placeholder and autofill.
- Content that must render identically in email or PDF. Restrict authors to a small named set of styles, or build it from a template.
Accessibility
06to keep
What the block ships with. Hold on to these as you make it yours.
- Named controlsEvery icon-only button keeps a text label, so a screen reader can say what it does.
- Keyboard firstEvery control is reachable with Tab, and its focus ring stays visible.
- More than colourA state never rides on colour alone; a mark or a word goes with it.
- Contrast holdsRetheme freely, but keep text at or above the contrast it ships with.
- Calm motionFor visitors who ask for reduced motion, things simply appear.
- Room to hitTargets stay at least 24px, with space between neighbours.
Notes for AI
1 line
Is all your assistant needs. With the Orvain MCP connected, it builds the block from your own tokens and components.
Add the Orvain “Comment thread” block to this page: header with title, count, people and ⋯, comments with avatar, verified seal, presence, Author pill, role tag, time and mention chips, composer with a grey tray: B I U S, colour, lists, link, code, @ mentions, emoji, attach, Send, ⌘↵ hint and count.
Works in
Questions about Comment thread.
What is the Comment thread block?
Comment thread is a Rich Editor block from Orvain UI, built for React and Vue with a matching Figma frame. Best for reviews and discussions where the reply matters most: read the thread, answer with full formatting.
What is the Comment thread block made of?
4 parts: header with title, count, people and ⋯; comments with avatar, verified seal, presence, Author pill, role tag, time and mention chips; composer with a grey tray: B I U S, colour, lists, link, code, @ mentions, emoji, attach, Send; and ⌘↵ hint and count. Keep them all, or drop the ones your product does not need; the rest of the block holds together without them.
Is the Comment thread block responsive?
Yes. It is drawn at 560px and never stretched past that. Below it, its controls, text and spacing step down with the container the block sits in rather than the browser window, so it holds up in a sidebar, a tablet layout and a 390px phone without clipping or sideways scrolling.
Is the Comment thread block accessible?
It ships with text labels on every icon-only button, full keyboard reach with a visible focus ring, states that never rely on colour alone, text contrast that holds when you retheme it, no animation for visitors who ask for reduced motion, and click targets of at least 24px.
How do I add the Comment thread block to my project?
It is part of every Orvain Library plan: the React and Vue code, its frame in the Orvain Figma file, and the Orvain MCP server. With the MCP connected, an AI assistant such as Claude Code, Cursor or v0 can build it from one line: “Add the Orvain Comment thread block to this page.”
When should I not use a Rich Editor block?
Text engineers will review in a diff. Markdown in a plain field stays readable in version control; rich output does not.
More Rich Editor blocks
All Rich EditorThe Orvain DispatchPremium components,
Premium components,
free in your inbox.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
Just components, never spam. You can unsubscribe anytime.
Orvain MCPComment thread
Comment thread is a Rich Editor block from Orvain UI, built for React and Vue with a matching Figma frame.
Best for
Reviews and discussions where the reply matters most: read the thread, answer with full formatting
Anatomy
Header with title, count, people and ⋯ · comments with avatar, verified seal, presence, Author pill, role tag, time and mention chips · composer with a grey tray: B I U S, colour, lists, link, code, @ mentions, emoji, attach, Send · ⌘↵ hint and count
Design review
2 commentsThread options
Reaction chips match the kit. Should the composer support @Cara style mentions?
Yes, and keep the full formatting: lists, links and inline code all work here.
Bold⌘B
Italic⌘I
Underline⌘U
Strikethrough⌘⇧X
Text color
Bulleted list⌘⇧8
Numbered list⌘⇧7
Link⌘K
Inline code⌘E
Mention@
Emoji
Attach file
In the Orvain Library
Get Comment thread for your product
The block’s code in React and Vue, its frame in the Figma file, and the Orvain MCP so your AI tools build with it. Part of every Library plan, alongside every other block.
- React
- Vue
- Figma frame
- Orvain MCP
About this block
Part of Rich Editor
What’s inside
04parts
The pieces it is built from. Keep them all, or drop the ones your product doesn’t need.
- Header with titlecount, people and ⋯
- Comments with avatarverified seal, presence, Author pill, role tag, time and mention chips
- Composer with a grey trayB I U S, colour, lists, link, code, @ mentions, emoji, attach, Send
- ⌘↵ hint and count
Responsive behaviour
560 px
Drawn at this width and never stretched past it. Below it, controls, text and spacing step down from the box the block sits in, not the window.
1440pxDesktop · 12 columns
When to use it
Where Rich Editor earns its place
Reach for Rich Editor
- Long-form content read as a page: documentation, articles, release notes.
- Replies where a quote or an @mention changes what the sentence means.
- Authors who will never learn markup and should not have to.
- A writing surface meant to stay clean until the writer selects something.
Reach for something else
- Text engineers will review in a diff. Markdown in a plain field stays readable in version control; rich output does not.
- A single line with no formatting, such as a title. Use a text input and keep its validation, placeholder and autofill.
- Content that must render identically in email or PDF. Restrict authors to a small named set of styles, or build it from a template.
Accessibility
06to keep
What the block ships with. Hold on to these as you make it yours.
- Named controlsEvery icon-only button keeps a text label, so a screen reader can say what it does.
- Keyboard firstEvery control is reachable with Tab, and its focus ring stays visible.
- More than colourA state never rides on colour alone; a mark or a word goes with it.
- Contrast holdsRetheme freely, but keep text at or above the contrast it ships with.
- Calm motionFor visitors who ask for reduced motion, things simply appear.
- Room to hitTargets stay at least 24px, with space between neighbours.
Notes for AI
1 line
Is all your assistant needs. With the Orvain MCP connected, it builds the block from your own tokens and components.
Add the Orvain “Comment thread” block to this page: header with title, count, people and ⋯, comments with avatar, verified seal, presence, Author pill, role tag, time and mention chips, composer with a grey tray: B I U S, colour, lists, link, code, @ mentions, emoji, attach, Send, ⌘↵ hint and count.
Works in
Questions about Comment thread.
What is the Comment thread block?
Comment thread is a Rich Editor block from Orvain UI, built for React and Vue with a matching Figma frame. Best for reviews and discussions where the reply matters most: read the thread, answer with full formatting.
What is the Comment thread block made of?
4 parts: header with title, count, people and ⋯; comments with avatar, verified seal, presence, Author pill, role tag, time and mention chips; composer with a grey tray: B I U S, colour, lists, link, code, @ mentions, emoji, attach, Send; and ⌘↵ hint and count. Keep them all, or drop the ones your product does not need; the rest of the block holds together without them.
Is the Comment thread block responsive?
Yes. It is drawn at 560px and never stretched past that. Below it, its controls, text and spacing step down with the container the block sits in rather than the browser window, so it holds up in a sidebar, a tablet layout and a 390px phone without clipping or sideways scrolling.
Is the Comment thread block accessible?
It ships with text labels on every icon-only button, full keyboard reach with a visible focus ring, states that never rely on colour alone, text contrast that holds when you retheme it, no animation for visitors who ask for reduced motion, and click targets of at least 24px.
How do I add the Comment thread block to my project?
It is part of every Orvain Library plan: the React and Vue code, its frame in the Orvain Figma file, and the Orvain MCP server. With the MCP connected, an AI assistant such as Claude Code, Cursor or v0 can build it from one line: “Add the Orvain Comment thread block to this page.”
When should I not use a Rich Editor block?
Text engineers will review in a diff. Markdown in a plain field stays readable in version control; rich output does not.
More Rich Editor blocks
All Rich EditorThe Orvain Dispatch
Premium components, free in your inbox.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
Just components, never spam. You can unsubscribe anytime.
