# WYSIWYG Plugin (again)

**URL:** https://meta.discourse.org/t/wysiwyg-plugin-again/39747
**Category:** Feature
**Tags:** completed
**Created:** [February 17, 2016, 6:18pm UTC](https://meta.discourse.org/t/wysiwyg-plugin-again/39747 "2016-02-17T18:18:46Z")
**Posts on this page:** 1
**Showing post:** 25

<div class="post-metadata">

### Author: ![ccdw](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ccdw/32/51564_2.png) [@ccdw](https://meta.discourse.org/u/ccdw)
#### Post date: [July 14, 2016, 9:40am UTC](https://meta.discourse.org/t/wysiwyg-plugin-again/39747/25 "2016-07-14T09:40:55Z")

</div>

> [@Rob\_Nicholson](#):
>
> Try explaining “escape codes” to a non-technical user…

Being able to disable markdown within comments would be a start - although in my view the original post content itself still needs the ability to add H1, H2, bold etc.

> [@P16](#):
>
> In a few months, one of us will get around to making a plugin for wysiwyg, so I guess we just have to be patient.

I was originally hopeful, but after considerable research I very much doubt that there is much appetite for this to be developed by third party developers, not least because of the ongoing maintenance issues associated with third party plugins. And if _maintenance_ isn’t proactive, imagine building up your community and then upgrading to an essential release only to find most of your existing posts are ill formatted.

Here’s Sam’s view on the scope of the _problem_ from [Who would prefer a standard wysiwyg to markdown?](https://meta.discourse.org/t/who-would-prefer-a-standard-wysiwyg-to-markdown/31340/53):

> [@Who would prefer a standard wysiwyg to markdown?](https://meta.discourse.org/t/who-would-prefer-a-standard-wysiwyg-to-markdown/31340/53):
>
> You got to have some perspective on the enormity of the problem.
> 
> A forum that has been, from day zero, WYSIWYG is probably reasonably straight forward to build and would only take 2-12 weeks of development as a plugin, there are real challenges around quoting, but quite a few options to shop from and you can strip out lots of features.
> 
> However, a WYSIWYG editor that co-exists with our Markdown hybrid editor is an impractical project to embark on. Going back and forth from Markdown to WYSIWYG is just too big of a project, and would always cause annoying reformatting of Markdown.
> 
> As it stands we have huge amounts of debt with our editor we got to repay, multiple weeks of engineering are required to move us to CommonMark, this is where we are going to invest our efforts. It would spread us way too thin to be also building a “WYSIWYG” option.
> 
> I much prefer investing effort in refining our current solution than jumping ship. There are tons of refinements left: “synchronizing” preview, to interacting and resizing images in preview.

---

_[View the full topic](https://meta.discourse.org/t/wysiwyg-plugin-again/39747)._