Actually its better to not mix non-resourceful routes with resourceful if you don't really need. And in this very case, you don't.
Actually its better to not mix non-resourceful routes with resourceful if you don't really need. And in this very case, you don't. Root :to => 'noodles#index' resources :noodles This is one you want, and you will have '/' and '/noodles' paths lead you to noodles#index, and that's what you suppose to want.
Take a look at your rake routes, you are creating something ugly ;) If you decide to curve out index route from noodles resource like in resources :noodles, :except => :index, you are also getting rid of noodles_path and noodles_url methods. The point of root is that you can change your mind about it, any time you want. Maybe it will be sign_up page, perhaps something different, maybe it won't change, but you don't want to loose that freedom.
Suppose the best solution would be to use root_url instead of noodles_url when trying to get to the index and using these routes root :to => 'noodles#index' resources :noodles, :except => :index So basically this just creates all routes, except for :index, because this route already exists as root. Then in the views just use root_url.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.