title: Django.contrib.flatpages without models
body: <p>I have some flatpages with empty <code>content</code> field and their content inside the template (given with <code>template_name</code> field).</p>
  
  <h3>Why I am using <code>django.contrib.flatpages</code></h3>
  
  <ul>
  <li>It allows me to serve (mostly) static pages with minimal URL configuration.</li>
  <li>I don't have to write views for each of them.</li>
  </ul>
  
  <h3>Why I don't need the model <code>FlatPage</code></h3>
  
  <ul>
  <li>I leave the content empty and just supply a template path. Therefore I can take advantage of having the source in a file;
  
  <ul>
  <li>I can edit the source directly from the file system, without the help of a server (such as admin).</li>
  <li>I can take advantage of syntax highlightning and other editor features.</li>
  </ul></li>
  <li>With the model I have to maintain fixtures for flatpages.
  
  <ul>
  <li>So the data for the same entity is in two seperate places.</li>
  <li>If I move the content inside the fixture it'll be more difficult to edit.
  
  <ul>
  <li>Even if fixture maintenance was a non-issue I'd still need to dump and load these fixtures again and again during development.</li>
  </ul></li>
  </ul></li>
  </ul>
  
  <h3>What I am looking for</h3>
  
  <p>Basically; getting rid of <code>FlatPage</code> model while maintaining <code>contrib.flatpages</code> functionality. I don't have a clear idea how this should be solved. If there's a clean way of modifying (like <code>add_to_class</code>) <code>FlatPages</code> to get the information somewhere other than the database I'd prefer that. Maybe the metadata can be inserted to the templates and then a special manager that reads this data would replace the default manager of <code>FlatPages</code>.</p>
  
  <p>If I don't prefer manual editing over admin functionality for flatpages, how can take the database out of the equation?</p>