<story><title>Wax: The Word Processor for the Web</title><url>https://waxjs.net/</url></story><parent_chain></parent_chain><comment><author>lewisjoe</author><text>I see this is built on top of the amazing Prosemirror richtext toolkit. I&amp;#x27;m a huge fan of Prosemirror&amp;#x27;s architecture which powers extremely customizable editors like this one.&lt;p&gt;But to call this component a word-processor - is a bit overkill. Why? To call an editor a word-processor it should support pagination &amp;amp; page layouts - as in Google Docs &amp;amp; Zoho Writer. Given the limited graphics capabilties of DOM, it is near impossible to build a paginated editor on top of the DOM.&lt;p&gt;Both Gdocs and Zoho Writer, do a tremendous amount of plumbing and keeps rendering logic out of browser&amp;#x27;s control to achieve a proper word processing experience on the web. Something like that can never be built upon contenteditable augumented frameworks like Prosemirror.&lt;p&gt;There are other players in this category that are building extensible editors without pagination - like Tiptap, Froala, CKEditor, etc. Except CKeditor, every other project is built on top of Prosemirror too!</text></comment>
<story><title>Wax: The Word Processor for the Web</title><url>https://waxjs.net/</url></story><parent_chain></parent_chain><comment><author>imiric</author><text>Seems interesting, we definitely need more advanced open source editors.&lt;p&gt;However, this gives off very unpolished vibes.&lt;p&gt;The demo renders poorly on mobile, with the textarea on the first page squished horizontally. The &amp;quot;Basic Editors&amp;quot; demo has the opposite problem, and there is horizontal scrolling with elements out of view. It&amp;#x27;s not clear if this is a fault of wax.js or of the demo page, but it&amp;#x27;s a bad first impression.&lt;p&gt;There is also a typo on the Features page:&lt;p&gt;&amp;gt; Select text and add a comment or particpate [...]</text></comment>