title: Git & Web-design: handling multiple customized templates
body: <p>I'm developing a CMS (with Django, but that doesn't matter) and have chosen GIT.</p>
  
  <p>Installations will vary in:</p>
  
  <ul>
  <li>Configs</li>
  <li>Database contents</li>
  <li>Media</li>
  <li>Templates</li>
  </ul>
  
  <p>First 3 are not a problem with git: we simply don't need these :)</p>
  
  <p>While developing, I have 1 default template with related media. 
  Later, each customer will receive his own design based on default templates (some slight customization). </p>
  
  <p>I'm not going to support each of the custom templates as I introduce new features. Modularity helps with this but is not a 100% solution.</p>
  
  <p>Do you have any experience to share?</p>
  
  <hr>
  
  <p>Example: Currently, v0.1 rocks: it has one 'default' template and 10 customized: one per customer.</p>
  
  <p>Now, in CMS v0.2 some new features has appeared: e.g. a login box. I tested it on the 'default' template, it works great &amp; I'm proud of it :) Now, all 10 customers want to have that great innovative login-box. Do I really have to update all that 10 customized templates manually?</p>