# editablejs/editable

🌱 A collaborative rich-text editor framework that focuses on stability, controllability, extensibility, and performance. 一款强到离谱的富文本编辑器框架，专注于稳定性、可控性、扩展性和性能。

Repository: https://github.com/editablejs/editable
Canonical: https://ross.abutalabs.com/products/editable
Homepage: https://docs.editablejs.com
Language: TypeScript
License: Apache-2.0
License Family: permissive
Topics: editable, react-editor, rich-editor, slate-editor, text-editor
Last push: 2024-10-15T03:22:58+00:00

## Health v2 (maintenance only)
Score: 23/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 0, release rhythm 8, longevity 100
- inputs: {"age_days": 1609, "days_push": 687, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1804, forks 125 (observed 2026-08-28T04:05:38.855980+00:00)

## What it is
Editable is an extensible rich-text editor framework for the web that replaces the native contenteditable attribute with a custom renderer, giving developers fine-grained control over selection, input, and cross-browser behavior. It ships as @editablejs/models (a document data model with operations) and @editablejs/editor (a React-based rendering layer with a plugin architecture), emphasizing stability, controllability, extensibility, and performance.

## Use cases
- embed a rich text editor in my react app
- build a wysiwyg editor without contenteditable bugs
- add collaborative text editing to a web application
- create a custom editor with plugins and a controllable document model
- avoid cross-browser selection and input issues in a text editor
- replace slate or quill with a more controllable editor framework

## When to choose
- you are building a custom rich-text editing experience in React and need fine-grained control over rendering and the document model
- native contenteditable quirks and cross-browser Selection/Input inconsistencies are blocking you
- you want a Slate-style data model with a plugin-based architecture and no reliance on contenteditable

## When to avoid
- your project does not use React, since the current version requires React for rendering (a native-DOM refactor is planned)
- you need a drop-in, pre-styled editor with minimal setup like Quill, CKEditor, or TipTap
- you only need plain text or simple markdown input, where a full editor framework is overkill
- you require a long-term frozen API, as the project states future refactors of its rendering layer are likely

## Facets
- artifact type: framework
- maturity: active
- function: editor, ui-components, plugin-system
- domain: web-development, frontend, text-editors
- platform: browser, cross-platform
- tags: rich-text-editor, wysiwyg, collaborative-editing, react, contenteditable-alternative, custom-renderer, typescript, slate-style-data-model, real-time

## Member repositories
- editablejs/editable (main) score 23

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:05:38.855980+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T03:21:48.741725+00:00, confidence not recorded.
  - readme: https://github.com/editablejs/editable (fetched 2026-08-28T04:05:38.855980+00:00, sha ab23cf1c9cea)
- Data as of 2026-08-30T08:39:29.467469+00:00.