the point is that you don't limit yourself from the outset by designing in code (i.e. you don't impose implementation restrictions that can be resolved with ima

the point is that you don't limit yourself from the outset by designing in code (i.e. you don't impose implementation restrictions that can be resolved with images/js/svg/whatever). it's a double edged sword, though, i don't think the article is exactly spot on here, you need to sort of bottom-up & top-down the whole process. The reason you mock up in psd (gross) or fireworks or a sketch book (yay!) or anywhere is because you can be purely expressive in an orthogonal capacity than you would be if you were implementing in code from the start. You ignore issues like "oh, will this p be in a div or in a series of lis contained by... blërg" while those implementation details are valid to keep in mind, they're not entirely crucial to address when you're sketching which is really the key word here.