# Summary outcome of the debate on wysiwyg?

**URL:** <https://meta.discourse.org/t/summary-outcome-of-the-debate-on-wysiwyg/41413>\
**Category:** Product Support\
**Created:** [3월 22, 2016, 10:14오전 UTC](https://meta.discourse.org/t/summary-outcome-of-the-debate-on-wysiwyg/41413 "2016-03-22T10:14:06Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![Rob\_Nicholson](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rob_nicholson/32/63483_2.png) [@Rob\_Nicholson](https://meta.discourse.org/u/Rob_Nicholson)\
**Post date:** [3월 22, 2016, 10:14오전 UTC](https://meta.discourse.org/t/summary-outcome-of-the-debate-on-wysiwyg/41413/1 "2016-03-22T10:14:06Z")

</div>

Continuing the discussion from [Who would prefer a standard wysiwyg to markdown?](https://meta.discourse.org/t/who-would-prefer-a-standard-wysiwyg-to-markdown/31340):

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](http://www.camra.org.uk) members is **very** high on our requirements.

---

_[View the full topic](https://meta.discourse.org/t/summary-outcome-of-the-debate-on-wysiwyg/41413)._