The true test of ProseMirror, SlateJS, and all these new augmented text-editors will not be comments, posts or even blog articles.
It will be Wikipages.
A visual editor for a wikipage is the crystallization of the semantic-content conflict as described eloquently by https://en.wikipedia.org/wiki/WYSIWYM
To date, despite a stream of donations and years of development, Wikimedia has failed to develop an editor that is better, by productivity and other lagging metrics, than just editing a text-field:
Increasingly, I believe what we really need is an enhanced markup editor-- where bolded text is bolded text, a quote is automatically highlighted as a quote, but links look like (check this link out)[http://example.com]. The ideal would be to forgo the "drop down to normal text editor" button and have the only & best way to edit be through the new editor.
Atlassian is experimenting with ProseMirror for their wiki—I think the configurable schema feature goes a long way towards solving this. (Coincidentally, Adrian, who is a contributor to ProseMirror, was one of the people who worked on WikiMedia's editor effort.)
We’re building the wiki engine https://www.nuclino.com based on Prosemirror. It would be great to get your feedback on it! I think a single editing mode is the way to go and Prosemirror's flexibility allows us to strike a great balance between usability for non-technical users (via menus) and speed for technical users (via markdown commands).
I'm glad you like the UI. Unfortunately, making the entire wiki public is not possible at the moment due to our focus on teams and companies. They use it to share knowledge internally and explicitly don’t want to have it indexed and publicly accessible.
It could be interesting though to expand Nuclino for the use in communities in the future as a lot of requirements overlap.
I couldn’t agree more. We were in the process of building our intuitive wiki platform (https://www.wikiful.com) when Marijn first announced ProseMirror. Seeing what a powerful tool it was, we decided to make it the backbone of our WYSIWYG editor.
Our goal was to create an editor intuitive enough to be accessible to the tech-unsavvy, while also curing the ills (slowness, plugin overload) that frustrate our tech colleagues who use current enterprise wiki products.
You’ve clearly put a lot of thought into what makes a great editor — any comments you have on Wikiful's editor would be much appreciated.
It will be Wikipages.
A visual editor for a wikipage is the crystallization of the semantic-content conflict as described eloquently by https://en.wikipedia.org/wiki/WYSIWYM
To date, despite a stream of donations and years of development, Wikimedia has failed to develop an editor that is better, by productivity and other lagging metrics, than just editing a text-field:
https://en.wikipedia.org/wiki/VisualEditor https://www.theregister.co.uk/2013/09/25/wikipedia_peasants_...
Increasingly, I believe what we really need is an enhanced markup editor-- where bolded text is bolded text, a quote is automatically highlighted as a quote, but links look like (check this link out)[http://example.com]. The ideal would be to forgo the "drop down to normal text editor" button and have the only & best way to edit be through the new editor.