3 ms·
Actually, your designer shouldn't be continuing to work on your mockups in the first place. After the mockup is complete, it gets turned into a template and th
by wccrawford 16y ago
Actually, your designer shouldn't be continuing to work on your mockups in the first place. After the mockup is complete, it gets turned into a template and then everyone works on that. The mockup was just a proof of concept to the customer. It wasn't meant to keep being used.
Also, be careful with your mockups. If you're demoing functionality, you don't want the looks of the site to be pretty, and if you're demoing the visual appearance, you don't want the site to work at all. If you mix the 2, the customer will get it in their head that most of the work is already done, when it's not even close.
- rue 16y ago> After the mockup is complete, it gets turned into a template and then everyone works on that. You should re-read the article, unless you're simply asserting that is the One True Way of doing it.
- audionerd 16y agoI agree with your arguments when the purpose of a mockup (Photoshop or otherwise) is for visual concept / art direction / client presentation. But when you move past that stage, and begin to integrate HTML/CSS with server code, things get messy real quick, and that's the problem I think this article is proposing to solve. I think the terminology may be confusing. For example, in the vernacular I'm familiar with, "mockups" are in Photoshop, "templates" are static HTML, and "views" run on the server. And even so, I find these terms are often used interchangeably.