title: Knockout.js Project Structure
body: <p>I have been looking at Angular.js and Knockout.js as potential front end solutions. I love Knockout's tutorials and documentation. However, it is not clear to me how Knockout handles templating larger applications.</p>
  
  <p>For example in Angular, you would make a main template like this:</p>
  
  <pre><code>&lt;div id="content" class="container" ng-view&gt;&lt;/div&gt;
  </code></pre>
  
  <p>And then this would be populated by by the "partials", for example:</p>
  
  <pre><code>&lt;p&gt;This is a partial&lt;/p&gt;
  </code></pre>
  
  <p>My question is, does Knockout support the same concept? It appears that Knockout wants to use the "foreach" template (<a href="http://knockoutjs.com/documentation/template-binding.html" rel="nofollow">http://knockoutjs.com/documentation/template-binding.html</a>). However, that does not address breaking the HTML down into smaller segments.</p>
  
  <p>Am I on the right track here? Is there something I am missing in regards to Knockout's directory structure?</p>
  
  <p><strong>EDIT:</strong> I have gotten some good feedback. My understanding is that Knockout does not have a templating solution built in. If this is true, then I will probably need Angular.</p>