Rails-doc.org 1.1 has just been deployed. It features:
- a revised front page with latest good notes
- search improvements
- fixes to some cache problems
- other minor fixes
We had a good first weekend and we are now getting a steady few thousand daily users. However, we still need more registered users to post more notes. I want to again thank Fabio Cevasco, who interviewed me and wrote an early review on Rails-doc. We also got noticed on Rails Inside and a dozen other blogs. Thanks to all who posted about us!
We got loads of nice and encouraging e-mails from users. We try to answer them as quickly as we can. Thanks for all the feedback!
Cool. Now that the search bug has been fixed I think I’ll use this as my primary Rails documentation site from now on. :)
Great work guys! This is definitely the best and the most usable Rails documentation project ever seen.
Keep on the good work!
Nice site but there is one show-stopper for me. Using googleapi for the JavaScript hosting. I am in the “Google knows too much already camp” so this site is essentially useless for me as it is blocked by noscript.
Any change of a self-hosted (Naturally unsupported since it is secondary) fallback if the googleapi link fails?
I’ve been using this since you guys launched and must say this is the first rails documentation site that I’ve been actually using more than once.
There’s only one problem. I have to login in every time I visit your site after I close my browser. Mainly I use this as a fluid app (SSB). I’ve tried this in other browsers and it has the same behavior (camino, firefox). Could you add a “remember me” feature?
- Mike
Definitely more enjoyable to search than the rails rdoc. I find the look appealing and easy to read. The search menu works great. Good work guys! Keep it up, it will surely become one of those assets you can’t do without.
@Hongli, Pekka, Patrick: Thanks!
@John Jones: I doubt that Google is gonna add much to their knowledge just by hosting JavaScripts. :) But we hear ya. We’ll look into falling back on local copies.
@MikeInaz: Thanks for pointing that out. We’ll definitely do something about it.