Dear fellow Ruby on Rails developers,
I found it cumbersome to search the net for Ruby on Rails plugins that
I need, every time I start a new Rails project. Today I launched a new
website:
http://www.railsplugins.net/
This is an index of Ruby on Rails plugins. There is nothing on it yet,
so if you have a plugin, please submit it. This website was written
in less than 24 hours in Ruby on Rails.
As with every index site, you can rate each plugin and post comments.
This website also has a unique feature: favorites. Each plugin that
you rate is automatically added to your favorites list (under the
assumption that one only rates plugins he/she uses). The plugins that
you have given the highest ratings will show up on top of your
favorites list. So if there are plugins that you use over and over
again, give them a high rating and you can easily find them by going
to railsplugins.net.
Whatโs wrong with http://agilewebdevelopment.com/plugins if I may ask?
Best regards
Peter De Berdt
Hm, I didn't know about that website.
So, a shorter URL I guess.
And on railsplugins.net you can register and submit a plugin in a
single form. There's no need to go through a separate registration
process before you can submit a plugin.
You don't need to register to create a plugin at http://agilewebdevelopment.com, either. It's a single form.
I already responded to the tail of this thread, but since I'm working my way backwards I'll respond to the head, too.
As you have learned from others since sending this email, there already is a Rails plugin directory at http://agilewebdevelopment.com/plugins/ that currently lists over 600 plugins, with ratings and favorites. Additionally, the combination of favorites at the directory and installing plugin packs via RaPT allows you to install all your favorite plugins in a new Rails project with one command.
Enjoy.
I'm gonna have to put in my plug for http://agilewebdevelopment.com/plugins/
since I use it every day, and I would like to see that community grow
and prosper rather than another one created. Consider the Rails
documentation situation.