I am building a product that has static pages and dynamic pages(product related). Both category of pages have different release life cycle. The marketing team working with the designer, release the static pages and the product pages are released by the engineering team.

The static pages reside in `public/home` and they are self contained. They don't need access to the Rails infrastructure other than providing links. 

In this setup, I am trying to implement the following behavior:

* When an un-authenticated visitor launches <http://www.xyz.com>, the user should be taken to the static landing page.
* When an authenticated visitor launches <http://www.xyz.com>, the user should be taken to the product landing page (LandingsController, index action).

In my current implementation, I check if the user is authenticated in the Rails world and render the static page OR the product page.

I want to know the following:

1) How do you handle such scenarios?

2) Is there a way to avoid entering the Rails stack for static home page.

3) Is there a customization for the root\_path method to return different root based on the context