I added too the result of running rails generate controller welcome index:
rails generate controller welcome index
route get "welcome/index"
I think it's important because without it, the user don't know which files are generated and that some routes are generated either.
[getting started] Update Setting the Application Home Page to show th…
…e get "welcome/index" route
lifo/docrails is an open repository for simple changes to documentation. Anyone can push to it. Unless @fxn asked you to submit a pull request here, it's not actually neccesary.
I used a pull request because I'm not just fixing a typo or a factual error, I'm changing (kinda) the structure of the some part of the guide, deleting and adding new content, I use the docrails If i'm adding a few text, for instance, for this rails/docrails@470c151, but I can do this in the docrails repo if that's better. @fxn what do you think?
Sounds legit! Just wanted to point that out.
@steveklabnik There are some confusion on what repo to use, maybe we should write a guide to clarify when we should use docrails and when the official repo, don't you think? @vijaydev @fxn
Look at the comments in another PR of mine: #6454
@steveklabnik thanks for that though
@rafmagana We do have a blog post from @fxn on this: http://weblog.rubyonrails.org/2012/3/7/what-is-docrails/
Our usual process in case of getting a PR for doc patches is to merge them (after review of course) and tell people that they can use docrails in the future, if they feel comfortable doing so. In case where people want eyeballs on their changes, they can always make PR in rails. The only thing we tell people not to do is make PR in docrails project (we would love GitHub to allow disabling PRs in projects).
As far as this PR is concerned, I'll have a look and merge it in.