# 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:** 110

<div class="post-metadata">

### Author: ![Ralf\_Stockmann](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ralf_stockmann/32/505867_2.png) [@Ralf\_Stockmann](https://meta.discourse.org/u/Ralf_Stockmann)
#### Post date: [April 10, 2025, 10:02pm UTC](https://meta.discourse.org/t/test-our-new-composer/352347/110 "2025-04-10T22:02:29Z")

</div>

Are there any plans to revisit the known issues of the #shared-edits Plugin with this new composer? Both in terms of missing features (showing edit-cursors of other people, group-based enabling of the feature etc.) and robustness (see e.g. [Shared-Edits Improvements - #18 by Ralf\_Stockmann](https://meta.discourse.org/t/shared-edits-improvements/232713/18) )?

I’m still hoping we can prevent to install a separate “Etherpad” like service like HedgeDoc to have “nice” shared edits and use a Discourse based solution for our intranet instead.

I’m also considering to write a new plugin which offers an “on the fly” shared edits experience based on [y.js](https://yjs.dev) with just a loose syncing…

---

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