I'd appreciate some guidence on how folks balance finding the right designer vs. the need to develop a DNN skin. Let me explain...

Over the years finding a designer with the right skills and whom we can trust has been one of the more challenging elements of running our business. The chance of finding such a designer who ALSO understands DNN skinning is less likely still. So, we've decided to focus on finding the right designer first - and then think about how to convert it to a DNN skin.

The designer part of "easy" (technically). Our designer will deliver a .PSD file or HTML/CSS. The problem is that he doesn't have any experience with DNN and, as such, won't be thinking about DNN-specific concepts such as containers and modules.

So, our current plan is to take that .PSD and have our developer skin it. But then we ended up paying "developer rates" to complete the skinning.

Is this the way most folks would do this, namely have the designer deliver a .PSD file and then pass off to a developer to skin it?

Thanks.

Mark

 Thank you, Westa. Yes, that's pretty much the philosophy we are following. The tricky part of this is that the designer is somewhat isolated from the implementation. In some respects that is not a bad thing at all but as pages are tweaked or enhanced it becomes a pretty cumbersome process to have to keep what the designer puts out in sync with the way it is "decomposed" into HTML/CSS.

I'd be curious to know if any of the DNN-specific guidelines or constraints are documented anywhere - a cookbook, of sorts, for the designer to follow.

Thanks again.

Mark