# 重新考虑作曲家——降低门槛

**URL:** <https://meta.discourse.org/t/rethinking-the-composer-lowering-the-bar/47333>\
**Category:** UX\
**Created:** [2016年七月14日 21:05 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:** 4

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [2016年七月14日 22:10 UTC](https://meta.discourse.org/t/rethinking-the-composer-lowering-the-bar/47333/4 "2016-07-14T22:10:46Z")

</div>

A “plain text only” mode is certainly the most viable outcome of that discussion. We’ve discussed simplifying the editor a fair bit:

> [@Should attaching an image be more obvious?](https://meta.discourse.org/t/should-attaching-an-image-be-more-obvious/31315/25):
>
> Well, I think he has a point, but to me it is mostly about this: If we decide we don’t care about teaching formatting codes, can we have a simplified, task oriented editor with three big honking buttons instead of 11 tiny toolbar buttons? It is basically these two things, opposed: traditional formatted text editor toolbar design [image] simplified task-based plain text design

And for anyone who has questions about Markdown, **share this URL far and wide**. (We do link that in every welcome PM as of March 2016 or so.)

### [Markdown Reference](http://commonmark.org/help)

---

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