title: Extend legacy site with another server-side programming platform best practice
body: <p>Company I work for have a site developed 6-8 years ago by a team that was enthusiastic enough to use their own private PHP-based CMS. I have to put dynamic data from one intranet company database on this site in one week: 2-3 pages. I contacted company site administrator and she showed me administrative part - CMS allows only to insert html blocks &amp; manage site map (site is deployed on machine that is inside company &amp; fully accessible &amp; upgradeable). </p>
  
  <ul>
  <li>I'm not a PHP-guy &amp; I don't want to dive into legacy hardly-who-ever-heard-about CMS engine </li>
  <li>I also don't want to contact developers team, 'cos I'm not sure they are still present and capable enough to extend this old days site and it'll take too much time anyway. </li>
  </ul>
  
  <p>I am about to deploy helper asp.net site on IIS with 2-3 pages required &amp; refer helper site via iframe from present site. New pages will allow to download some dynamic content from present site also. </p>
  
  <p>Is it ok and what are the pitfalls with iframe approach? </p>