Forms

Rich Text Editor

Toolbar-based contentEditable rich text editor supporting bold, italic, underline, strikethrough, and list formatting.

Quick Preview

Content

Installation

# No extra dependencies

// Copy component from
src/components/forms/RichTextEditor.tsx

Usage

import RichTextEditor from '@/components/forms/RichTextEditor'

<RichTextEditor
  label="Article Body"
  placeholder="Start writing..."
  onChange={(html) => setContent(html)}
/>

Prompt Preview

Copy a prompt that recreates this UI

Paste this into your AI coding assistant to generate code that closely matches the reference, including color, size, shape, typography, spacing, and polish.

Copy-ready AI prompt

Starts from the current visual reference and project constraints.

Build a forms component named Rich Text Editor in React/Next.js.
Goal: recreate the same overall UI and behavior as the Rich Text Editor reference from a component gallery.
What it needs to communicate: Toolbar-based contentEditable rich text editor supporting bold, italic, underline, strikethrough, and list formatting..

Project constraints:
- Use Next.js 16.2.6 with the App Router, React 19, TypeScript strict mode, and Tailwind CSS v4.
- Do not create a tailwind.config.js file. Use Tailwind v4 utilities and CSS variables where design tokens are needed.
- If you are implementing this inside the same project, use the Prompt font via next/font/google. If not, use the closest equivalent typeface.
- Return production-ready code with imports, responsive behavior, keyboard accessibility, and polished empty, hover, focus, active, and disabled states where relevant.
- Match the reference closely: color palette, spacing scale, border radius, shadows, icon scale, typography hierarchy, and motion timing.

Component-specific expectations:
- Support label, helper, error, disabled, and validation states.
- Ensure keyboard usability and accessible form semantics.
- Avoid unnecessary dependencies unless the behavior truly requires them.
- No explicit color literals were found in the examples. Match the live reference and the project accent color when appropriate.

Props to support:
- label: string — Label above the editor
- value: string — Initial HTML content
- onChange: (html: string) => void — Called with HTML string on input
- placeholder: string — default "Start typing..." — Placeholder text
- className: string — Additional CSS classes

Reference usage patterns:
- No examples were documented. Infer a sensible default presentation and one richer usage example.

Feature expectations:
- Bold, italic, underline, strikethrough
- Ordered and unordered lists
- contentEditable based
- HTML output
- Toolbar with execCommand

Output requirements:
- Return complete code, not pseudocode.
- Include all necessary imports and helper types.
- Keep the implementation accessible, responsive, and visually finished.
- Match the reference for color, size, shape, typography, spacing, and interaction states as closely as possible.
- If multiple files are needed, organize them cleanly and explain the file structure briefly.

Tweak only product-specific copy or data after the first generation pass.

Props

Prop	Type	Default	Description
`label`	`string`	-	Label above the editor
`value`	`string`	-	Initial HTML content
`onChange`	`(html: string) => void`	-	Called with HTML string on input
`placeholder`	`string`	`"Start typing..."`	Placeholder text
`className`	`string`	-	Additional CSS classes