When using Areas with MVC2 is it good practice for an area to have its own Content folder?

Question

I have an MVC2 application that is divided into Areas. Is it good practice for each area to have its own Content folder for Images, Styles etc that only pertain to that area?

Answer 1

Having used areas for a while each with its own Content folder for area specific items it seems to work well and we have come across no problems associated with it.

Answer 2

Mostly irrespective of your areas, you entire application will have similar look and feel. In that case your content could be shared across areas. In your case if every area gets a different look and feel then you can have content specific to that area. However I am sure you don't have that scenario.