Squire
Squire is an HTML5 rich text editor, which provides powerful cross-browser normalisation, whilst being supremely lightweight and flexible. It is built for the present and the future, and as such does not support truly ancient browsers. It should work fine back to around Opera 10, Firefox 3.5, Safari 4, Chrome 9 and IE8. Unlike other HTML5 rich text editors, Squire was written as a component for writing documents (emails, essays, etc.), not doing wysiwyg websites. If you are looking for support for inserting form controls or flash components or the like, you'll need to look elsewhere. However for many purposes, Squire may be just what you need, providing the power without the bloat.
Learn more
Trix
Compose beautifully formatted text in your web application. Trix is an editor for writing messages, comments, articles, and lists, the simple documents most web apps are made of. It features a sophisticated document model, support for embedded attachments, and outputs terse and consistent HTML. Most WYSIWYG editors are wrappers around HTML’s contenteditable and execCommand APIs, designed by Microsoft to support live editing of web pages in Internet Explorer 5.5, and eventually reverse-engineered and copied by other browsers. Because these APIs were never fully specified or documented, and because WYSIWYG HTML editors are enormous in scope, each browser’s implementation has its own set of bugs and quirks, and JavaScript developers are left to resolve the inconsistencies. Trix sidesteps these inconsistencies by treating contenteditable as an I/O device: when input makes its way to the editor, Trix converts that input into an editing operation on its internal document model.
Learn more
Editor.js
Next generation block styled editor. Meet the new editor, on our webpage you can see it in action. It is a block-styled editor, it returns clean data output in JSON, and it is designed to be extendable and pluggable with a simple API. Workspace in classic editors is made of a single contenteditable element, used to create different HTML markups. Editor.js workspace consists of separate Blocks: paragraphs, headings, images, lists, quotes, etc. Each of them is an independent contenteditable element (or more complex structure) provided by Plugin and united by Editor's Core. There are dozens of ready-to-use Blocks and the simple API for creation any Block you need. For example, you can implement Blocks for Tweets, Instagram posts, surveys and polls, CTA-buttons and even games. Classic WYSIWYG-editors produce raw HTML-markup with both content data and content appearance. On the contrary, Editor.js outputs JSON object with data of each Block.
Learn more
VisualEditor
The VisualEditor project by the Editing team aims to create a reliable rich-text editor for MediaWiki. VisualEditor is available as a MediaWiki extension using the Parsoid project to supply HTML+RDFa; however, its core implementation can be run without any of MediaWiki, Parsoid, or Node.js. As of 2020, the visual editor is available to all users at MediaWiki.org and on almost all Wikipedias and Wikivoyages. On most other Wikimedia projects and languages, it is available as an opt-in Beta Feature to logged-in users. VisualEditor is only available in some namespaces, including the main namespace, but generally not in discussion or template namespaces. The decline in new contributor growth was viewed as the single most serious challenge facing the Wikimedia movement. VisualEditor was built with the goal of removing avoidable technical impediments associated with Wikimedia's editing interface, as a necessary pre-condition for increasing the number of Wikimedia contributors.
Learn more