Bayon Text Editor docs
A guided overview of the Bayon Text Editor package, its document model, and the docs section.
Overview
Bayon Text Editor exists because authored content deserves more than a raw textarea and app teams deserve more than a pile of editor-specific edge cases. It gives you a polished writing surface, a stable block model, and the utility layer needed to save, render, inspect, and protect documents.
Editing that feels like a product feature, not a textarea
Headings, paragraphs, quotes, code, dividers, checkboxes, empty-block insertion, selection formatting, and block controls are packaged as one controlled React surface.
Render the exact content you save
The read-only renderer consumes the same `RichTextBlock[]` contract as the editor, so previews and published views do not drift from stored data.
Utilities for real app boundaries
Sanitization, plain-text extraction, Markdown conversion helpers, writing stats, and session helpers keep host apps from reinventing fragile document plumbing.
Designed for serious host apps
The package stays framework-neutral. Your product owns storage, uploads, permissions, routes, analytics, and save policy while the editor owns document interaction.
Examples that feel like real product work
Each example is a separate page with its own live editor state, not a duplicated screenshot. Use them to evaluate how the package behaves across product writing, knowledge capture, and AI-assisted review.
Product Brief
A launch-note style document with headings, narrative copy, quotes, checkboxes, code, stats, preview, and plain-text extraction.
Open exampleResearch Notes
A research-note document with concise observations, quotable claims, follow-up tasks, and code-like data extraction notes.
Open exampleAI Review Draft
A review-ready draft that demonstrates how host apps can keep AI prompts, review tasks, and final prose in the same structured document.
Open example