The discussion revolves around the need for a simpler markdown editor in Discourse to improve usability for non-technical users, particularly in a community with an older demographic. Rob_Nicholson proposes a hybrid editor inspired by Fasthosts’ community, which offers a basic WYSIWYG interface with a toggle to advanced markdown mode, preserving markdown functionality while simplifying the experience for most users. erlend_sh requests visual examples, which Rob_Nicholson provides, showing a clean, minimal toolbar and a markdown mode that correctly interprets syntax like #1. He notes the system appears to be Oracle/Lithium. Others, including XieLong and Deepit_Purkayastha, express support and interest in such a feature, with Deepit_Purkayastha seeking updates or plugins. spirobel reveals a related effort, a beginner-friendly editor discussed in a separate thread here, which Deepit_Purkayastha acknowledges.
Hypothetical and yes I know, potentially volatile subject but my old hobby horse - the markdown editor and non-technical users. I don’t want to go over old ground but this continues to be a bit of a blocker for adoption of Discourse in our mainly over 50 CAMRA forum - it’s not going away
I’ve just used the Fasthosts beta community recently and thought to myself “this is a nice little editor, simple and effective”. I noticed a little menu box bottom left which opens up the usual limited editing options like bold, italic etc.
But there is an advanced button on there which to my surprise reveals that this community is based upon markdown. I can’t comment how effective switching between the two is but would it be feasible for something similar in Discourse?
I see this as a win-win situation. The markdown detractors are happy as they have a nice simple editor for 99% of the time and the technical camp are happy because it’s still markdown under the hood.
Could you share some screenshots (better yet, screengrabs) of the editor UX you’re talking about? Not many people are gonna bother signing up to that website just to have a look at some buttons
I entered some text that gets interpreted as markdown and it prefixed it correctly. For example, people often put #1 at the start of a line which turns it into a header. In this editor, #1 worked as expected and when I switched to advanced/markdown it had been prefixed as \#1
I asked on the community if the moderators knew which system it was and they said Oracle. Zero knowledge of Oracle these days but maybe it’s Lithium?
Interesting enough, I had the same request in my newly transferred community just the other day - mainly because our old solution had an rich text editor.
I completely agree with @Rob_Nicholson I think this compromise with a simpler viewer but markdown under the hood is a great solution.
This looks like a very interesting solution… @sam@codinghorror@erlend_sh@XieLong
Anyone did any further work on this? Any plugins / extensions available. Can more people bump this discussion up ? Or are there any alternate discussions that I can’t find…
This help in a huge jump in adoption…