# Should Features be Core or Plugin

**URL:** <https://meta.discourse.org/t/should-features-be-core-or-plugin/15567>\
**Category:** Feature\
**Created:** [12. Mai 2014 um 16:39 UTC](https://meta.discourse.org/t/should-features-be-core-or-plugin/15567 "2014-05-12T16:39:34Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![mcwumbly](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mcwumbly/32/103861_2.png) [@mcwumbly](https://meta.discourse.org/u/mcwumbly)\
**Post date:** [12. Mai 2014 um 16:46 UTC](https://meta.discourse.org/t/should-features-be-core-or-plugin/15567/2 "2014-05-12T16:46:20Z")

</div>

> [@Mittineague](#):
>
> Perhaps the best way is to have anything not “essential” be a plugin, and when a certain number of users find that plugin useful then consider incorporating it into the Core?

There’s a 3rd approach in the mix too: Features that are implemented as plugins, but ship by default with the [standard install](https://meta.discourse.org/t/142537?silent=true) (eg, the emoji plugin and the docker plugin)

---

_[View the full topic](https://meta.discourse.org/t/should-features-be-core-or-plugin/15567)._