I think that we've probably all seen situations all across the spectrum - but ideally I think that HTML/CSS creation and prototyping belong earlier in the process, so that interative design can take place and as mentioned above, when it's time to implement the system (theming in Drupal, .aspx in .NET, whatever) it's generally MUCH simpler to do - and you get the benefit of testing/tweaking/designing around real, working HTML.
Of course, if it's a really good department/shop then the team of IA/UX/Visual Design/HTML/CSS/Development is all working together with a really good, balanced lead, right? ;) Cheers everyone, and happy Friday- Jason . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=41475 ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... disc...@ixda.org Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
