DokuWiki Prosemirror Plugin

A modern approach on DokuWiki WYSIWYG

User Tools

Site Tools

Trace:
en:why

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
en:why [2018/07/30 11:23] – Andreas Gohren:why [2018/07/30 11:24] – Andreas Gohr
Line 1: Line 1:
 ======= Why a new WYSIWYG plugin? ====== ======= Why a new WYSIWYG plugin? ======
  
-A [[https://www.dokuwiki.org/plugins?plugintag=wysiwyg#extension__table|series of plugins]] attempting to integrate a WYSIWYG editor into DokuWiki. [https://www.dokuwiki.org/plugin:ckgedit|CKGEdit]] maintained by Myron Turner is probably the most popular.+There are a [[https://www.dokuwiki.org/plugins?plugintag=wysiwyg#extension__table|series of plugins]] that attempt to integrate a WYSIWYG editor into DokuWiki. [[https://www.dokuwiki.org/plugin:ckgedit|CKGEdit]] maintained by Myron Turner is probably the most popular.
  
 To understand why the approach of CKGEdit and similar plugins is not ideal for wikis, we need to take a deeper look at the details... To understand why the approach of CKGEdit and similar plugins is not ideal for wikis, we need to take a deeper look at the details...
Line 22: Line 22:
 This means that the editor itself has to know exactly what the Wiki system behind it can do in order to limit the input accordingly.  This means that the editor itself has to know exactly what the Wiki system behind it can do in order to limit the input accordingly. 
  
-This is exactly the approach the [https://prosemirror.net/|Prosemirror]] toolkit takes. Prosemirror is a library that provides the basic mechanisms for a WYSIWYG editor, but makes no assumptions about the input and output format. Instead, the editor works internally with an abstract model of the edited document. A schema defines how this document can be structured.+This is exactly the approach the [[https://prosemirror.net/|Prosemirror]] toolkit takes. Prosemirror is a library that provides the basic mechanisms for a WYSIWYG editor, but makes no assumptions about the input and output format. Instead, the editor works internally with an abstract model of the edited document. A schema defines how this document can be structured.
  
 The editor converts the document to HTML for display and returns user input back to the document. When saving, the abstract document is converted back into syntax - since the schema already ensures that the document is well-formed, this last step is comparatively trivial. The editor converts the document to HTML for display and returns user input back to the document. When saving, the abstract document is converted back into syntax - since the schema already ensures that the document is well-formed, this last step is comparatively trivial.
en/why.txt · Last modified: 2018/07/30 11:25 by Andreas Gohr
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki