# Attn: Gem developers - a documentation project

**URL:** <https://www.ruby-forum.com/t/attn-gem-developers-a-documentation-project/88577>\
**Category:** Rails\
**Created:** [March 12, 2007, 8:32pm UTC](https://www.ruby-forum.com/t/attn-gem-developers-a-documentation-project/88577 "2007-03-12T20:32:14Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![nelson](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/dec6dc/32.png) [@nelson](https://www.ruby-forum.com/u/nelson)\
**Post date:** [March 12, 2007, 8:32pm UTC](https://www.ruby-forum.com/t/attn-gem-developers-a-documentation-project/88577/1 "2007-03-12T20:32:14Z")

</div>

Hi,

I’m currently working on a project called Basedex which I’ve announced  
previously on this list, and to rehash, it’s basically a collaborative  
index. Right now, I’m developing an index[1] for Ruby on Rails  
developers to search through all the APIs for Ruby on Rails and gems.

I would love to consolidate all the APIs for all the gems into one  
place, so if you wish to have your rdoc documentation included into  
Basedex, please send the URL of your documentation (e.g.  
[api.rubyonrails.org](http://api.rubyonrails.org)) by either replying to this post or by e-mailing me  
at nelson[at]speran[dot]com. Right now, I’m simply parsing  
fr\_class\_index.html and fr\_method\_index.html.

Here are a few indexes that I’ve created:  
Facets API - [http://blazingrails.basedex.com/index/173](http://blazingrails.basedex.com/index/173)  
Hpricot API - [http://blazingrails.basedex.com/index/174](http://blazingrails.basedex.com/index/174)  
Rake API [http://blazingrails.basedex.com/index/193](http://blazingrails.basedex.com/index/193)  
scRUBYt API - [http://blazingrails.basedex.com/index/185](http://blazingrails.basedex.com/index/185)  
mechanize API - [http://blazingrails.basedex.com/index/192](http://blazingrails.basedex.com/index/192)

I’ve merged the indexes that I think most Ruby on Rails developers would  
use (Hpricot, Rake, scRUBYt, mechanize) into [1]. In the future, I hope  
to have this automated.

Thanks,  
Nelson

[1] [http://blazingrails.basedex.com/index/64](http://blazingrails.basedex.com/index/64)