# Suggestion in how to package and distribute Ember Components **URL:** \ **Category:** Design\ **Created:** [May 9, 2014, 11:36am UTC](https://discuss.emberjs.com/t/suggestion-in-how-to-package-and-distribute-ember-components/5196 "2014-05-09T11:36:28Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![henriquea](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/henriquea/32/15534_2.png) [@henriquea](https://discuss.emberjs.com/u/henriquea)\ **Post date:** [May 9, 2014, 11:36am UTC](https://discuss.emberjs.com/t/suggestion-in-how-to-package-and-distribute-ember-components/5196/1 "2014-05-09T11:36:28Z")
I’m working on a few components which will be shared across different products. I’m thinking in use `bower` to manage the packages but one possible downside is to have one repository for each component. Does anyone have any suggestion or is doing something similar? ---
**Author:** ![michiel](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/michiel/32/9462_2.png) [@michiel](https://discuss.emberjs.com/u/michiel)\ **Post date:** [July 28, 2014, 7:16pm UTC](https://discuss.emberjs.com/t/suggestion-in-how-to-package-and-distribute-ember-components/5196/2 "2014-07-28T19:16:35Z")
You might want to take a look at [GitHub - realityendshere/emberella-component-blueprint: A starting point for creating new, more portable Emberella components.](https://github.com/realityendshere/emberella-component-blueprint) > The goal of the Emberella Component Blueprint project is to streamline the process of creating individual Ember components, modules, or “micro-projects.” It is intended as a starting point (or project template) for developers to build their own fully-tested, modular Ember Components. Announced here [Repo as a blueprint (boilerplate) for authoring components to distribute](http://discuss.emberjs.com/t/repo-as-a-blueprint-boilerplate-for-authoring-components-to-distribute/5370) by @pixelhandler