A deprecated rich text editor framework for the web platform with patches for browser inconsistencies and a plugin-based architecture.
Scribe is a rich text editor framework for the web platform that patches browser inconsistencies and provides sensible defaults. It was originally developed by The Guardian for their CMS but is now deprecated, with no plans for new features. The framework uses a plugin-based architecture, allowing developers to extend its functionality easily.
Web developers and teams building CMS or content editing tools who need a customizable rich text editor with browser inconsistency fixes. It's suitable for those willing to fork and maintain the project, as it's no longer actively developed.
Developers choose Scribe for its lightweight, plugin-based design and comprehensive patches for browser inconsistencies in `contenteditable`. Its no-dependency approach and transaction-based DOM manipulation offer control and reliability for rich text editing.
DEPRECATED: A rich text editor framework for the web platform
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Scribe patches numerous browser inconsistencies in contenteditable and native command APIs, as documented in the BROWSERINCONSISTENCIES.md file, reducing cross-browser debugging headaches.
Everything is a plugin, allowing easy customization and extension; the architecture section emphasizes this modular approach for adding functionality like blockquote commands or toolbars.
It is lightweight with no external dependencies, simplifying integration and reducing bundle size, which is highlighted in the core features and installation sections.
DOM manipulations are wrapped in transactions to capture state changes, enabling reliable undo/redo management through the optional custom undo manager, as described in the architecture.
Scribe is officially deprecated with no new features planned, and only critical updates may be provided, limiting its long-term viability and feature set.
The README admits to significant missing documentation, forcing developers to rely on reading the source code or sparse wiki pages for implementation guidance.
It only actively supports a subset of browsers, detailed in the GitHub Wiki, which may not cover modern or legacy browser requirements without additional work.
Users are encouraged to fork the project for any feature work, adding the burden of maintaining and updating the codebase independently, as stated in the deprecation notice.