# Repensando o Composer - abaixando o padrão

**URL:** <https://meta.discourse.org/t/rethinking-the-composer-lowering-the-bar/47333>\
**Category:** UX\
**Created:** [Julho 14, 2016, 9:05pm UTC](https://meta.discourse.org/t/rethinking-the-composer-lowering-the-bar/47333 "2016-07-14T21:05:17Z")\
**Posts on this page:** 1\
**Showing post:** 5

<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:** [Julho 14, 2016, 11:21pm UTC](https://meta.discourse.org/t/rethinking-the-composer-lowering-the-bar/47333/5 "2016-07-14T23:21:16Z")

</div>

Excuse my ignorance but why can’t an editor be implemented that uses markdown behind the scenes but is WYSIWYG? There was a similar thread over on StackOverflow:

> <https://stackoverflow.com/questions/12840132/integrated-markdown-wysiwyg-text-editor>

It was mentioned that the CKeditor now can work in markdown. Even if CKeditor isn’t fit for purpose, surely the team behind Discourse could considering writing their own? How hard can it be 😉

I accept (even if I don’t understand the technicalities) that switching between HTML and Markdown is problematic but if Markdown has a future, then a good WYSIWYG editor would be an ideal companion?

---

_[View the full topic](https://meta.discourse.org/t/rethinking-the-composer-lowering-the-bar/47333)._