Headless editor
The editor runs with no toolbar. Your application supplies the buttons, reads the state the editor reports, and exports the content in the format it needs.
Your buttons
Active at the caret: none
Exports
0 words, 0 characters
Loading the editor…
Full UI editor or headless?
RichTextEditor is one engine with two front ends. Choose the full UI when you want a finished editor. Choose headless when your application already has its own toolbar and design system and needs only the editing engine.
| Concern | Full UI editor | Headless |
|---|---|---|
| Toolbar | Built in, configured with toolbar options | None. Your own buttons call run() |
| Formatting | Toolbar, menus and keyboard shortcuts | run(command, value) from your own controls |
| Knowing what is active | Shown on the toolbar | isActive(name), can(command) and update events |
| Exporting content | getHTML, getText, getMarkdown, getJSON | The same methods |
| Best for | A finished editor you can drop in | A custom toolbar, your own design system, or a non-browser UI |
See the full UI editor demos for the complete toolbar, or the JavaScript API demo for the programmatic surface both modes share.