title: ASP.NET content/functionality versus design/layout/styling
body: <p>When developing a web application using ASP.NET, do you have any hints about how to separate the development of content/functionality from the design, so that the two can be developed separately and in parallel?</p>
  
  <p>The situation is:</p>
  
  <ul>
  <li>Customer has agreed on what functionality they want</li>
  <li>Customer is changing their mind about the appearance (styling and layout) of the pages</li>
  <li>Web designer is non-expert:
  
  <ul>
  <li>Isn't developing clean CSS-based layout from scratch</li>
  <li>Is taking various table-based layouts (with CSS) from 3rd-party sites, to use as an example/prototype of the layout to discuss with the customer</li>
  </ul></li>
  </ul>
  
  <p>Given this, how to start coding the functionality before the table-based layout is finalized?</p>
  
  <p>I thought that one way to do it might be:</p>
  
  <ul>
  <li>Code the functionality (which includes creating the active elements on each page) without caring about (specifying) their layout and styling</li>
  <li>Then, at the end, after the designer and the customer have agreed on a design, then cut-and-paste the active elements into the designer's prototype pages.</li>
  </ul>
  
  <p>Is this the only or the best way to do it? What other ways are there? Any hints, tips, or tricks to make this easier?</p>