# Separate bundles in reusable components

**URL:** <https://forum.mautic.org/t/separate-bundles-in-reusable-components/26065>\
**Category:** Ideas and Feature Requests\
**Created:** [November 13, 2022, 10:05pm UTC](https://forum.mautic.org/t/separate-bundles-in-reusable-components/26065 "2022-11-13T22:05:20Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![xmontero](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/xmontero/32/7499_2.png) [@xmontero](https://forum.mautic.org/u/xmontero)\
**Post date:** [November 13, 2022, 10:05pm UTC](https://forum.mautic.org/t/separate-bundles-in-reusable-components/26065/1 "2022-11-13T22:05:21Z")

</div>

I’ve seen in the source code (v4.x) that there a number of bundles: LeadBundle, CampaignBundle, EmailBundle, FormBundle…

> **[mautic/app/bundles at 024d80c4e0c22f7db6adae4955f518763a9482dd · mautic/mautic](https://github.com/mautic/mautic/tree/024d80c4e0c22f7db6adae4955f518763a9482dd/app/bundles)**
>
> 024d80c4e0c22f7db6adae4955f518763a9482dd/app/bundles

I wonder if we should take a symfony approach and make each bundle a reusable standalone component living in separate repos, so the mautic project becomes mainly a `composer require`of all them.

At the same time, that approach would enable that if a person wants to build a completely different project using the “only the forms component”, or the campaigns component, etc she should be able to do it.

Q1: Are there any active development lines in that direction?

and if not,

Q2: If any coder starts a fork to separate that into reusable components would that be welcome for a PR in the main mautic project?
