title: What process does professional website building follow?
body: <p>I've searched for a while, but I can't find anything related on Google or here.</p>
  
  <p>Me and some friends were debating starting a company, so I figure it might be good to do a quick pilot project to see how well we can work together. We have a designer who can do HTML, CSS and Flash, enjoys doing art, but doesn't like to do HTML and CSS... And 2 programmers that are willing to do anything.</p>
  
  <p>My question is, from an experienced site builder's perspective, what steps do we do - in chronological order - to properly handle a website? Does the designer design the look and feel of the site, then the programmers fill in the gaps with functionality? Or do the programmers create a "mock-up" of the site with most of the functionality, then the designer spices it up? Or is it more of a back-and-forth process?</p>
  
  <p>I just want to know how a professional normally handles it.</p>
  
  <p><strong>Update:</strong>
     A recap taking some of the notes from each post.</p>
  
  <blockquote>
    <p>Step 1: Define requirements. What will your site/application do?</p>
    
    <p>Step 2: Use cases. Who will use the application, and what will they do with it? This doesn't have to be done with a bunch of crazy UML diagrams, just use whatever visual aids you think work best for you. Find a CMS vendor, or a search vendor, or both. While planning, maybe do some competitor analysis, and see how those in similar fields have done theirs.</p>
    
    <p>Step 3: Visual proof-of-concept. This is done by your designer, NOT your programmers... Programmers are notoriously bad at UI. Use an image program like Photoshop, not an HTML editor. Leave it fluid and simple at first. Select the three-color theme for the site (two primaries and an accent.) Get a sense of how you want to lay things out, keeping in mind the chosen CMS and/or search functionality. Focus hard on usability, add pizzaz later. Turn the created concept into JPEG mock-ups, or create a staging site to allow the client to view the work. A staging site will allow for future releases to be tested prior to moving it to production.</p>
    
    <p>Step 4: Once the site is conceptualized by your designers, have your HTML/CSS developer turn it into markup. He/she should shoot for XHTML compliance and test on as many major browsers as you can. Also a good time to set up versioning/bug tracking/management systems, to keep track of changes, bugs, and feedback.</p>
    
    <p>Step 5: Have your programmers start turning your requirements into software. This can and should be done in parallel with Step 4- there's no reason they can't be coding up the major pieces and writing tests while the UI is designed and developed.</p>
    
    <p>Step 6: Marry up the final UI design with the code. Test, Test, Test!!</p>
    
    <p>Step 7: Display end result to client, and get client sign-off.</p>
    
    <p>Step 8: Deploy the site to production.</p>
    
    <p>Rinse, Repeat...</p>
  </blockquote>