Rich Text Editor
Prov1.0.0A Tiptap rich text editor with toolbar, slash menu and live Markdown or HTML.
Build for your project
Code/install build
Usage
Import it and pass your content. The props that matter most are listed next.
Example
"use client";
import { RichTextEditor } from "@/components/ui/notchset/rich-text-editor";
export function RunNotes({ notes, save }: { notes: string; save: (markdown: string) => void }) {
return <RichTextEditor defaultValue={notes} wordLimit={120} onChange={({ markdown }) => save(markdown)} />;
}Props
defaultValue–string (HTML)Starting content; RESET restores it.
onChange–({ html, markdown, json }) => voidEvery change.
wordLimit–numberOver it, the count turns signal.
source–booleanThe Markdown / HTML pane (default on).
Anatomy
- Built on Tiptap's StarterKit: one file serves both builds.
- Notes are blockquotes with a NOTE label and a top rule, not a side bar.
- toMarkdown(json) gives the Markdown lines, if you need them elsewhere; for HTML use the editor's own getHTML().
RichTextEditordata-slot="rich-text-editor"The editor, toolbar, menus and source.
Source
components/ui/notchset/rich-text-editor.tsx
This component is included with Pro.
Try the live preview above. Get Pro to install the source.
Build for your project
Code/install build
Installation
pnpm dlx shadcn@latest add @notchset-pro/rich-text-editorNeeds your registry key. Your components.json style picks the Base UI or Radix build: radix-*, new-york and default get Radix, base-* gets Base UI.
Styles didn't apply?
The CLI adds the styles to the CSS file named in components.json (tailwind.css). Check that it points at your global stylesheet, that the project uses Tailwind CSS v4, and that the file is imported in your root layout. Installed by hand: paste styles.css into that file.
For coding agents
Give your coding assistant the Markdown guide instead of screenshots.
Use it for
- Writing short structured documents (notes, release notes, briefs) that are stored as Markdown or HTML
Use something else when
- A single line or plain text: use Input or Textarea
Mistakes to avoid
- Store Markdown or HTML from onChange, not the source pane's text
Agents find it by
- rich text editor, wysiwyg, markdown editor, tiptap, release notes, document editor, notes, Notchset
Where agents read it
- Guide for this component: https://notchset.dev/md/rich-text-editor.md
- Every component, for tools without MCP: /llms.txt
- MCP server:
https://notchset.dev/api/mcp(setup)
Behaviour
Keyboard
- ⌘B / ⌘I / ⌘E
- Bold / italic / inline code
- ⌘Z / ⇧⌘Z
- Undo / redo
- /
- Slash menu on an empty line
- ↑ ↓ Enter Esc
- Move, insert, close the slash menu
- Alt+F10
- Into the selection's format bubble
- ← → Home End
- Between toolbar keys
- Esc (in the bubble)
- Back to the text
Accessibility
- Tiptap's contenteditable textbox with a label; toolbar buttons expose aria-pressed
- Buttons keep the editor's selection (no focus steal); the slash menu is a listbox the document points at (aria-controls, aria-activedescendant)
- Each toolbar is one tab stop; arrows, Home and End move between keys (mirrored in RTL); a narrow toolbar scrolls
Motion
- Bubble menu
- Fades in and settles up 4px (260ms)
- Slash menu
- Unrolls from the top (clip-path, 300ms); the highlight glides (140ms)
- Source
- The changed line flashes and fades (900ms)
Responsive
- The two panes stack under 720px.
Performance
- Toolbar state reads through useEditorState, so typing doesn't re-render the whole card.
Changelog
v1.0.0 · 2026-10-02
First release
Part of
Included with Pro
Pro is in early access.
