title: Strategies for deploying Django App
body: <p>I have a question that is probably more general than django-related development.  The background is quite simple:</p>
  
  <p>I am working on a project whose pages are mostly associated with a web application (this is what I am using Django for).  In addition to the app-related pages, however, there are quite a few auxiliary pages (like a landing page, a faq page, a contact page, etc.) that have basically nothing to do with the web app.  </p>
  
  <p>What is the standard strategy for deploying such a project?  It seems flawed to route requests to these static pages through Django.  What seems to make sense is running two servers: one responsible for running the Django app and a a separate server that is responsible for serving the static pages (including, perhaps, the static content used by the app portion of the web site) .  </p>
  
  <p>What are some guiding principles that should be employed when making these decisions?</p>