What's wrong with just directing new people to "Agile Web Development with Rails"?
So long as you keep the API documentation up to date, I think professional, fulltime writers and educators can write better introductory documentation than any of us. On Dec 14, 2:02 am, August Lilleaas <[EMAIL PROTECTED]> wrote: > I disagree that a forum and/or mailing list rocks - it's good enough, > but it's not awesome. Having a system where questions are tagged and > moderated is very different. > > Also, keep in mind what kind of questions people might have. In IRC, > some guy wondered why restful_authentication didn't work. He had > installed the plugin, and login/logout worked, but "a users could > still see the posts other users have made". When I told him that he > needed to change the finders in the controller to find the posts from > the current user (current_user.posts), he said "that didn't work" - > because he hadn't set up a Post.belongs_to :user and > User.has_many :posts. He had no idea on how to achieve this. > > You could say that this was pretty retarded, and I would agree. He > simply didn't understand anything about how rails works, and when I > told him that he needed to set up the associations, he came back to me > and asked why he got all these error messages - he hadn't added a > user_id column to the posts table, and didn't understand why he had to > do that. Still, after some moderations and tagging, and with an added > write-up on how to do what he wanted to do - authenticate users and > then scope finders by the current user - would be a good resource for > rails beginners. You could argue that it's not up to the core team to > document usage of plugins, but then again why not? Most Rails books > include some plugin usage, and pretty much all rails apps are using > plugins anyway. > > I could just get at it, and make this railsbeginners.com, but that's > pointless because of the reasons mentioned above - we don't need > another one-man doc site, we need a doc team, listed on > rubyonrails.com/core. > > On Dec 14, 9:38 am, Michael Klishin > > <[EMAIL PROTECTED]> wrote: > > But it may not get right feel of the framework for a newcomer, and as > > long as Rails is opinionated software, Djangish kind of a book may be > > a good idea to fill in this gap. > > > On 14 дек. 2007, at 10:02, Manfred Stienstra wrote: > > > > Long story short: good API docs, good examples, screencasts, blog > > > posts and a forum/mailinglist seem like the way to go and I think > > > we're already pretty well supplied in those areas. > > > > Manfred > > > MK --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
