# Repensando o Composer - abaixando o padrão **URL:** \ **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:** 1
**Author:** ![Mittineague](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mittineague/32/114259_2.png) [@Mittineague](https://meta.discourse.org/u/Mittineague)\ **Post date:** [Julho 14, 2016, 9:05pm UTC](https://meta.discourse.org/t/rethinking-the-composer-lowering-the-bar/47333/1 "2016-07-14T21:05:17Z")
There are several topics here where members have asked for a more complex feature rich editor, or have expressed problems as a result of Markdown syntax not being understood. > [@WYSIWYG Plugin (again)](https://meta.discourse.org/t/wysiwyg-plugin-again/39747/24): > > normal users don’t expect something weird to happen when they type a letter. if they press “#” then they expect “#” to appear on the screen - always. I’m wondering if having a “text as plain text only” default with an option to use Markdown syntax might help? I understand how Markdown works. I fail to see the need to have “styling” options which to me are more appropriate for blog posts than they are for topic discussion. But perhaps even what options that are currently available are too much for the typical member to grasp and would be better moved to an “advanced user” option. That is, instead of someone unfamiliar with anything more than plain text needing to learn Markdown to make a plain text post look like plain text, they would need to proactively choose to use Markdown syntax, the assumption being that they understand how to use it before they use it. I know work on the editor is slated, so now may be a better time to bring up this idea before a lot of code is (re)written. --- _[View the full topic](https://meta.discourse.org/t/rethinking-the-composer-lowering-the-bar/47333)._