# I propose to make a new plugin

**URL:** https://meta.discourse.org/t/i-propose-to-make-a-new-plugin/52291
**Category:** UX
**Created:** [November 1, 2016, 10:55am UTC](https://meta.discourse.org/t/i-propose-to-make-a-new-plugin/52291 "2016-11-01T10:55:17Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [November 1, 2016, 1:09pm UTC](https://meta.discourse.org/t/i-propose-to-make-a-new-plugin/52291/3 "2016-11-01T13:09:32Z")

</div>

This kind of work is slotted for native theme support

> [@Native theme support](https://meta.discourse.org/t/native-theme-support/47494):
>
> At the moment Discourse supports 3 mechanisms for amending the “theme” of a Discourse instance: Plugins Plugins can amend both backend and frontend code. They are the most advanced level of customisation. Advantages: Can change backend or frontend Straightforward to distribute, live on Github Disadvantages: Tricky to install as it requires a container rebuild High risk as it is allowed to amend backend code Hard to isolate to a single site In a multisite environment admin on master site m…

---

_[View the full topic](https://meta.discourse.org/t/i-propose-to-make-a-new-plugin/52291)._