# Has anyone used the PluginAWeek Version?

**URL:** <https://www.ruby-forum.com/t/has-anyone-used-the-pluginaweek-version/120175>\
**Category:** Radiant CMS\
**Created:** [November 14, 2007, 2:48pm UTC](https://www.ruby-forum.com/t/has-anyone-used-the-pluginaweek-version/120175 "2007-11-14T14:48:17Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jeff\_Dean](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/53a042/32.png) [@Jeff\_Dean](https://www.ruby-forum.com/u/Jeff_Dean)\
**Post date:** [November 14, 2007, 2:48pm UTC](https://www.ruby-forum.com/t/has-anyone-used-the-pluginaweek-version/120175/1 "2007-11-14T14:48:17Z")

</div>

Has anyone played around with [http://api.pluginaweek.org/mini\_radiant/](http://api.pluginaweek.org/mini_radiant/)?

It sounds like a great idea - and it seems like it would make it a lot  
easier to port existing rails apps - something like:

- piston all of the plugins
- update some configs to fix the load order
- run some migrations

On my end, the fact that everything in radiant has to be an extension  
is proving very tough for me. I have 10+ plugins in each of my rails  
apps, and loading them into radiant is a chore - and if any other  
extensions ever use similar plugins, it seems like it could cause  
trouble.

I’ve spent a while now trying to learn extensions, so I don’t really  
want to make the switch unless it really makes sense. Anyone have any  
feedback on the mini-radiant?

Jeff
