Is a controller called "home" sort of a standard or best practice?

Is it pretty much a standard, best practice or just a good idea to create a controller called “home” and put, say, my web sites home page (‘index.html.erb’) there??

Well, the name of the controller can differ, but yes, that’s how most apps render their homepage.

Some call it home, some call it welcome, root, etc, whatever. It is
common practice to have SOME kind of controller, just because you need
a controller (unless the page is completely static), to hold common
top-level pages like Home, About, Terms & Conditions, Privacy Policy,
"Thanks for visiting, come back soon" (i.e., you just logged out),
etc. etc. etc.

-Dave

One action to rule them all, one action to find them. One action to
bring them all and in the darkness bind them.

Is it pretty much a standard, best practice or just a good idea to create a
controller called "home" and put, say, my web sites home page
('index.html.erb') there??

Some call it home, some call it welcome, root, etc, whatever. It is
common practice to have SOME kind of controller, just because you need
a controller (unless the page is completely static), to hold common
top-level pages like Home, About, Terms & Conditions, Privacy Policy,
"Thanks for visiting, come back soon" (i.e., you just logged out),
etc. etc. etc.

-Dave

Naturally, Ryan Bates has a RailsCast about this:

http://railscasts.com/episodes/117-semi-static-pages
http://railscasts.com/episodes/117-semi-static-pages-revised

(That second one might require a membership to see, not sure, didn't want to log out to find out.)

Walter

Revised and pro eoisides require a membership which is about 10 USD a month.

Bye,
Norbert

PREEEECCCCIIIIOUUUUSSSSSSS!!! MY PREEECCCCIOUUUSSSSSSSSSS!!!!