# פיתוח תוספים מהיר יותר על ידי הפרדת ה-frontend לרכיב ערכת נושא

**URL:** <https://meta.discourse.org/t/developing-plugins-faster-by-separating-the-frontend-into-a-theme-component/211638>\
**Category:** Development\
**Created:** [9 בדצמבר,‏ 2021,‏ 5:47pm UTC](https://meta.discourse.org/t/developing-plugins-faster-by-separating-the-frontend-into-a-theme-component/211638 "2021-12-09T17:47:40Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![JQ331](https://avatars.discourse-cdn.com/v4/letter/j/41988e/32.png) [@JQ331](https://meta.discourse.org/u/JQ331)\
**Post date:** [9 בדצמבר,‏ 2021,‏ 7:40pm UTC](https://meta.discourse.org/t/developing-plugins-faster-by-separating-the-frontend-into-a-theme-component/211638/3 "2021-12-09T19:40:46Z")

</div>

> [@merefield](#):
>
> so I still think that ultimately a single plugin install is still the best approach for open source work of that nature

Yeah there are certainly situations when ultimately you want a single codebase. The lightbulb moment I had was that even if I want a single codebase in the end, I could code all the front end stuff in the theme component, and then once that’s working, move it to the plugin. A little tedious, but overall way better for me because I’m still spending most of my time coding in the theme component work flow.

---

_[View the full topic](https://meta.discourse.org/t/developing-plugins-faster-by-separating-the-frontend-into-a-theme-component/211638)._