# Plugin Examples

**URL:** <https://discuss.rubyonrails.org/t/plugin-examples/10299>\
**Category:** rubyonrails-talk\
**Created:** [March 15, 2007, 4:06pm UTC](https://discuss.rubyonrails.org/t/plugin-examples/10299 "2007-03-15T16:06:40Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Peter\_De\_Berdt](https://avatars.discourse-cdn.com/v4/letter/p/53a042/32.png) [@Peter\_De\_Berdt](https://discuss.rubyonrails.org/u/Peter_De_Berdt)\
**Post date:** [March 15, 2007, 4:06pm UTC](https://discuss.rubyonrails.org/t/plugin-examples/10299/1 "2007-03-15T16:06:40Z")

</div>

Rails plug-ins generally don’t work well for encapsulating a complete module (e.g. full CRM module with views, controllers, …), but are great for extrapolating specific common functionality you’re using throughout your applications (e.g. adding extra javascript\_helpers, …).

If you want to share complete modules between your applications, you can look into Rails Engines ([http://rails-engines.org](http://rails-engines.org)/). I believe this will change (or maybe already has) in the next version of Rails, as it is evolving to a core framework where you add plugins for specific functionality (e.g. the in\_place\_editor will become a plugin in Rails 2.0). You might look into the mephisto blog code, I believe it implements extensibility by adding extra modules.

Best regards

Peter De Berdt