Umbraco Application Arcitecture
<p>We are reengineering our web site and are thinking of using Umbraco for building a CMS web site. Here is the braod architecture we are thinking of using :-</p>

<ol>
<li><strong>Development Architecture</strong> :-  Integrate Umbraco in Visual studio project using NUGet package manager. Here both ASP.NET MVC5 and NUGet package manager will be used in the same solution but as different web projects. To elaborate it more there will be following two projects :- </li>
</ol>

<p>a. First Project for Umbraco Back Office Site where content writers will be creating pages, administrators will be creating Document Types, Templates etc </p>

<p>b. Second Project for ASP.Net MVC team which will be creating Partial Views, writing business rules etc. All the macros created in this project will then be integrated in to the pages to be created in Umbraco Back Office Site. </p>

<ol start="2">
<li><strong>Deployment Architecture</strong> :- Single site will be created in IIS in which Umbraco back office site and the site for the outer world will be hosted, i.e. all the DLLS related to both the projects described above will be copied to the single physical folder on the web server.  For Umbraco back office site we will be creating a special url which will not be accessible to the outer world.
Changes in Web.config of the ASP.NET MVC project will be copied to the Umbraco back office site web.config. </li>
</ol>

<p>Please have a look at the this broad architecture and let us know what are the pros a cons of this architecture</p>