Topic: Mixed index pages
Typically, I've seen that you generate all your controllers and then route the route of your app to one of them. That way when you're on localhost:3000 you're actually looking at one of your controllers that handles the main functions.. i.e. localhost:3000/products or some such thing.
I have an app I'm writing where the homepage (index) will pull data from a bunch of different tables, aggregating it into one nice summary view. Since data is coming from lots of places there's really no great candidate for what to choose when setting up the route to '/'. I guess I could either:
a. Pick one arbitrarily. Since it's restful, I'd choose a restful controller.
b. Create a controller specifically for the job (homepage controller or something). Since it's job would be just to display just on the front page it would be non-restful.
Most of my previous rails experience has been around just getting stuff to work, so I'm only now actually taking the time to think through things like this. Patience appreciated..