A rich editor is a text surface where formatting belongs to the text itself rather than being typed as markup: bold, headings, lists and quotes live in the document, and the toolbar reports what is under the cursor. Orvain's Rich Editor family holds six, a document page with its toolbar pinned above, a comment thread whose composer sits under the replies, a page whose formatting pill follows the selection, and three toolbars on their own: one pill carrying everything, a large-control row for touch, and a segmented pair that splits type settings from formatting.
Buttons are the small half of this component. The work is in the round trip: the toolbar has to re-read the selection on every cursor move, and a control that takes focus when pressed collapses the selection it was meant to act on, so the controls have to refuse focus rather than claim it. Paste is the other half. Text arriving from elsewhere carries styles your document has no rules for, and an editor without a paste filter slowly fills with fonts nobody chose.
An internal handbook page where the author needs headings for structure, a checklist for the procedure and a quote for the caveat. Whatever a reader later searches for has to survive being pasted in from somewhere else.
Comments on a document, where each reply can bold the term under discussion, quote the line it answers and tag whoever owns it. The composer stays inline under the thread rather than opening a modal.
A task body written once and read many times: a summary, bulleted steps to reproduce, a link to the build. The formatting row sits underneath so the field opens on the text, not on its controls.
A marketing surface where a non-technical editor writes into a field the layout owns. The editor offers the marks the template renders and nothing more, so the page cannot be broken from inside the CMS.
Use rich editing when the author's job is writing rather than engineering, and when what they see while typing has to match what publishes. Use Markdown when the text is reviewed as source, versioned alongside code, or written by people who already know the syntax. The tell is the audience: content maintained by engineers ages better as plain text.
Convert it into your own document model instead of accepting the incoming HTML as it arrives. Keep the marks your schema names (bold, links, headings, lists) and drop everything else, including inline fonts, colours and sizes inherited from whatever application the text came from. Offer a paste-as-plain-text shortcut too, because often the author wants only the words.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
A rich editor is a text surface where formatting belongs to the text itself rather than being typed as markup: bold, headings, lists and quotes live in the document, and the toolbar reports what is under the cursor. Orvain's Rich Editor family holds six, a document page with its toolbar pinned above, a comment thread whose composer sits under the replies, a page whose formatting pill follows the selection, and three toolbars on their own: one pill carrying everything, a large-control row for touch, and a segmented pair that splits type settings from formatting.
Buttons are the small half of this component. The work is in the round trip: the toolbar has to re-read the selection on every cursor move, and a control that takes focus when pressed collapses the selection it was meant to act on, so the controls have to refuse focus rather than claim it. Paste is the other half. Text arriving from elsewhere carries styles your document has no rules for, and an editor without a paste filter slowly fills with fonts nobody chose.
An internal handbook page where the author needs headings for structure, a checklist for the procedure and a quote for the caveat. Whatever a reader later searches for has to survive being pasted in from somewhere else.
Comments on a document, where each reply can bold the term under discussion, quote the line it answers and tag whoever owns it. The composer stays inline under the thread rather than opening a modal.
A task body written once and read many times: a summary, bulleted steps to reproduce, a link to the build. The formatting row sits underneath so the field opens on the text, not on its controls.
A marketing surface where a non-technical editor writes into a field the layout owns. The editor offers the marks the template renders and nothing more, so the page cannot be broken from inside the CMS.
Use rich editing when the author's job is writing rather than engineering, and when what they see while typing has to match what publishes. Use Markdown when the text is reviewed as source, versioned alongside code, or written by people who already know the syntax. The tell is the audience: content maintained by engineers ages better as plain text.
Convert it into your own document model instead of accepting the incoming HTML as it arrives. Keep the marks your schema names (bold, links, headings, lists) and drop everything else, including inline fonts, colours and sizes inherited from whatever application the text came from. Offer a paste-as-plain-text shortcut too, because often the author wants only the words.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.