What is best practice on ASP.NET MVC projects and extensionable/skinned systems?

Question

I've been wondering about best practices on creating a project in MVC, and let others create extension/modules/plugins and skins/themes etc, for it.

For example WordPress is great at this. Just upload a file or folder. Or even browse the plugins directly from your WP administration and install by a simple click.

Does anybody here have a few tips on how to create a project that allows that flexibility. For the skins I might need to implement my own viewengine, right?

Any good resources and tips would be great.

Thanks!

Answer 1

I ended up using a VirtualPathProvider since I wanted the views outside of the application. Now, we made it possible for the views to be stored in the database.