# Package a Discourse plugin as a gem

**URL:** <https://meta.discourse.org/t/package-a-discourse-plugin-as-a-gem/273036>\
**Category:** Developers\
**Tags:** plugin-guides, how-to\
**Created:** [July 27, 2023, 11:41am UTC](https://meta.discourse.org/t/package-a-discourse-plugin-as-a-gem/273036 "2023-07-27T11:41:29Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)\
**Post date:** [July 27, 2023, 3:34pm UTC](https://meta.discourse.org/t/package-a-discourse-plugin-as-a-gem/273036/3 "2023-07-27T15:34:17Z")

</div>

> [@hawm](#):
>
> Seems this approach not possible to cover any Discourse theme stuff in plugin?

That’s correct, you need to handle the front end JS framework stuff separately

> [@hawm](#):
>
> Maybe a better title is “Package a Discourse specific Rails Engine as a gem”

Whilst technically accurate, I wouldn’t agree that title would be better as that would put some of the right people off from reading the Topic: most people who write plugins might not identify them as “Discourse specific Rails Engines”

I actually more regularly separate my code into back end plugins and front end theme components now so I can iterate the front end stuff very quickly on deployments to staging and production environments.

---

_[View the full topic](https://meta.discourse.org/t/package-a-discourse-plugin-as-a-gem/273036)._