# Plugin WYSIWYG (otra vez)

**URL:** https://meta.discourse.org/t/wysiwyg-plugin-again/39747
**Category:** Feature
**Tags:** completed
**Created:** [17 Febrero, 2016 18:18 UTC](https://meta.discourse.org/t/wysiwyg-plugin-again/39747 "2016-02-17T18:18:46Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![ccdw](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ccdw/32/51564_2.png) [@ccdw](https://meta.discourse.org/u/ccdw)
#### Post date: [24 Febrero, 2016 13:09 UTC](https://meta.discourse.org/t/wysiwyg-plugin-again/39747/7 "2016-02-24T13:09:00Z")

</div>

I’m putting my investigation into the above on hold until I get a better understanding of the new Plugin API and topic virtual DOM architecture

In the meantime, please don’t let that stop you continuing with your discussions should you wish to..

> [@A versioned API for client side plugins](https://meta.discourse.org/t/a-new-versioned-api-for-client-side-plugins/40051):
>
> Later today I am going to be merging our [new post rendering engine](https://meta.discourse.org/t/help-us-test-our-new-post-rendering-engine/39221/101) into master. Swapping out Ember/HTMLBars for a virtual-dom based renderer provides us with a huge performance increase, but it also has the side effect of being incompatible with how plugins were previously made. While doing this work, it occurred to me that we made a fairly big mistake in the past by not providing a mechanism for versioning the public APIs used by client side code. We used to encourage people to just dump in w…

---

_[View the full topic](https://meta.discourse.org/t/wysiwyg-plugin-again/39747)._
