Summary outcome of the debate on wysiwyg?


(Rob Nicholson) #1

Continuing the discussion from Who would prefer a standard wysiwyg to markdown?:

The above discussion was pretty busy and the thread is now closed with some comment about a proof of concept. To save me having to read all 77 posts, could somebody kindly give me a summary of the next steps? Don’t want to kick start the discussion again - just a summary of where Discourse is going on this subject and maybe a time frame?

If there is a vote, then a BIG vote for a wysiwyg option. As a programmer and reader of Coding Horror, I’m well aware of the back story, positives etc but usability and familiarity for 180,000 non-technical www.camra.org.uk members is very high on our requirements.


(ljpp) #2

I think Jeff put it very clearly here:

I have a high(ish) traffic, yet low user count, non-tech forum and the editor has not been a concern for my audience. And yes, they have raised lots of other concerns, but I don’t think that the editor/wysiwyg thing was never brought up. The new forum was constructed as an open community project, so they all had opportunities to contribute (and they did).

We migrated from SMF.


(Jeff Atwood) #3

If that’s the case, then you should be voting yourself away from Discourse – very far, far away :wink:


(ljpp) #4

@Rob_Nicholson

How far from WYSIWYG the Discourse actually is today?

You have the UI buttons for basic message formatting, and a real-time updated preview panel. So in practice What You See Is What You Get. Out of the box.


(Rob Nicholson) #5

I’m sad you feel that way Jeff. I’ll pass that back to the evaluation team - basically no plan to implement a Google Mail like interface?


(Jeff Atwood) #6

There are zero plans for that in the forseeable future. If pure WYSIWYG is an absolute bedrock must-have requirement, the sooner you look elsewhere, the happier you will be.


(Rob Nicholson) #7

This is actually one of the biggest concerns raised.


(Jeff Atwood) #8

This was really all summarized in the earlier discussion, so feel free to read it for specifics. No reason to duplicate it all here again.


(Jeff Atwood) #9