title: Development methodology for CMS driven websites
body: <p>This is quite a generic question, and I hope to hear what opinions people have on this, rather than a dedicated answer.</p>
  
  <p>Ive been developing for about 6 years and have recently joined a new team. I am self taught. I have been given a project to develop a Magento driven ecommerce site, and a large portion focussing on editorial/blogging sections.</p>
  
  <p>When I work with a CMS (i realise not CMS's work the same), to complete a project my methods have always been in the following order:</p>
  
  <ol>
  <li>Develop the front-end (html, css, js).</li>
  <li>Integrate front-end templates onto CMS</li>
  <li>Compile CMS functions to fill out contents in placeholders on thos templates (replacing any dummy text etc).</li>
  <li>Inject content.</li>
  </ol>
  
  <p>When I explained this to my colleagues they looked horrified.</p>
  
  <p>So they work a different way around:</p>
  
  <ol>
  <li>Compile functions on CMS</li>
  <li>Inject content.</li>
  <li>Add styles (html templates, css, js etc).</li>
  </ol>
  
  <p>Add to the equation, my scenario, the ecommerce website im developing must be responsive on devices.</p>
  
  <p>So my question is, having I been doing this wrong for the last 6 years? Complete the front-end first? Or compile the front-end after?</p>
  
  <p>I would really like to hear what people think about this. I am self taught, so have never had official training on development patterns such as this.</p>
  
  <p>Thanks</p>