title: How to best manage Django templates & static content?
body: <p>So, my team and I are new to Django development. We've been trying to design our project structure over the last couple weeks, and we've done a lot of reading to try and get a grasp of the best practice of doing this.</p>
  
  <p>However, we are still struggling to get our heads around the best way to store our templates/static files that are generic to all applications.</p>
  
  <p>Let me detail our structure we've implemented so far:</p>
  
  <pre><code>root-folder/
      app-1/
          static/
              app-1/
                  css/
                  js/
                  img/
          templates/
              base.html
              base-app-1.html **extends base.html
      app-2/
          static/
              app-2/
                  css
                  js
                  img
          templates/
              base.html **extends base.html at 'project-name' level
              base-app-2.html **extends base.html
      project-name/
          collectstatic/
          templates/
              base.html
      static/
          base/
              css
              js
              img
  </code></pre>
  
  <p>The one thing that bugs me with this structure is that our top level templates reside inside the 'project-name' level. I would like to see this folder at the same level as our root level static folder. </p>
  
  <p>However, I don't want to move the root level static folder content into 'project-name/collectstatic' because I don't want to have files inside that folder being version controlled.</p>
  
  <p>We realise that there is no definitive answer to this problem in the Django world. But, are we on the right lines? Have we misunderstood something?</p>
  
  <p>A couple ideas we've got are:</p>
  
  <ol>
  <li>To have an app dedicated to top level templates and htdocs called something along the lines of 'general' or 'generic'.</li>
  <li>To move the 'project-name/templates' dir to the root level along side our 'static' folder there.</li>
  <li>To stop talking about this problem and go with the structure drawn out above.</li>
  </ol>