# Test our new composer!

**URL:** <https://meta.discourse.org/t/test-our-new-composer/352347>\
**Category:** Announcements\
**Tags:** composer\
**Created:** [March 12, 2025, 11:48am UTC](https://meta.discourse.org/t/test-our-new-composer/352347 "2025-03-12T11:48:22Z")\
**Posts on this page:** 1\
**Showing post:** 102

<div class="post-metadata">

**Author:** ![manuel](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/manuel/32/468169_2.png) [@manuel](https://meta.discourse.org/u/manuel)\
**Post date:** [April 2, 2025, 7:40pm UTC](https://meta.discourse.org/t/test-our-new-composer/352347/102 "2025-04-02T19:40:09Z")

</div>

> [@lindsey](#):
>
> I think it’s likely that we’ll offer a user preference to enable the Markdown toggle, but that is not set in stone at this point. Appreciate you sharing your opinion here though, it’s helpful input.

> [@lindsey](#):
>
> At this point, we do not have specifics on how both versions of the composer will be supported longterm (e.g., whether composer type will continue to be controlled by site setting, left up to user preference, or something else).

I’d find it best if the availability of composer type can be set as a site setting. And when both are enabled, users can pick their composer in a user preference.

I wouldn’t like the toggle option on the composer as a longterm feature. It makes perfect sense now for testing on meta, but it would pretty much go against the goal of simplifying the composer experience.

---

_[View the full topic](https://meta.discourse.org/t/test-our-new-composer/352347)._