title: .NET CMS. Shall we build or use existing one
body: <p><strong>Hi All,</strong></p>
  
  <p>In a new project we have a requirement to build a CMS. As this is big organization and requirement is designed a CMS system with SOA which can provide common publishing (view) for various applications. Some of the applications need to develop, some already there in .NET (very slow) and some of them are in classic ASP which needs to migrate to .NET.
  CMS is very first application which need to develop. So question is as below:</p>
  
  <p><strong>1)Shall we develop and new CMS from scratch (using MVC, Angular etc.) or shall we use something existing e.g. Umbraco or Dotnetnuke</strong> </p>
  
  <p>We are in initial stage and exploring options. Of course using Umbraco will save time but what type of limitations can be there in future? Is it easily expandable? </p>
  
  <p>Anyone has experience using .NET related CMS?</p>
  
  <p>Cheers</p>